-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for moving this project repo under kubernetes-sigs #23
Comments
It's funny that exactly today I am having this exact conversation in the sig-auth meeting. Please join and show that you are supporting this 🙂 . |
Was there any progress made in turning this into a SIG project? I'm definitely in support of this |
I'd still like to make this happen and there were no objections when I last attended sig-auth, I just haven't had the time to follow up on it. |
I know that it was recently (Feb 2nd) discussed in SIG Auth: https://docs.google.com/document/d/1woLGRoONE3EBVx-wTb4pvp4CI7tmLZ6lS26VTbosLKM/edit# |
@camilamacedo86, we pitched it to sig-auth again (on the 2nd of Feburary, 2022) and the process started. Currently we have a review as a first next step: |
I will close the issue as being stale. Feel free to reopen it, if it is still an issue. |
bumps to kube 1.19.2 and picks up our carries to apiserver package
We (Kubebuilder team) are planning to use
kube-rbac-proxy
for adding authn/authz support to the metrics endpoint exposed by the controllers written using Kubebuilder. We would like to avoid forking the repo and maintaining our own container images.kube-rbac-proxy is a very useful project and having the repo and the container images available under kubernetes will benefit other OSS projects. Have you considered it moving it under
kubernetes-sigs
?The text was updated successfully, but these errors were encountered: