Krzysztof Ostrowski

Can you squash also the commits into one or two (e.g. one for the github action and one for the other stuff)? :smile:

@lucacome, If you don't want to continue working on this, I would take your PR over and finish the last comments. I really like your work here

Closing in favor of https://github.com/brancz/kube-rbac-proxy/pull/395

Hi everyone, Apologies for my delayed response. Summer vacations are in full swing here in Europe! Regarding the logging flags: they've been deprecated by k8s upstream. As a result, they're...

@Sajiyah-Salat, I am one of the maintainers. @brancz is not involved in its development. He was kind enough to let us migrate the project to sig-auth. You can reach out...

## TLS Certs To maintain the exact same current behavior, you can generate a self-signed TLS certificate and provide it to the kube-rbac-proxy either within the container image or using...

Cert-Manager isn't a necessity by itself. Obviously it is the best overall solution. A better solution would be to create a cert with a CA and put the cerst in...

/assign @nilekhc

/retest-required

/retest-required