-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Update kube-rbac-proxy to v0.8.0 release #1785
Comments
Hi @hectorj2f, It has been done manually. @DirectXMan12 @vincepri @droot could you please give a hand with this one? |
Thanks @camilamacedo86. |
@DirectXMan12 @vincepri @droot Is there any way I could help with the release process/tagging for this new kube-rbac-proxy release 🙏🏻 ? |
Hi @hectorj2f, In the Currently has a little people with the requires access to push the images, so @DirectXMan12 would like to address it via automation instead of we still manually doing this work. @paulfantom, could you give a hand to us to achieve it? So, far as a workaround, you can update your manager manifest yaml files to use the https://github.com/brancz/kube-rbac-proxy released images directly instead of it. |
We need to the same that is done in https://github.com/brancz/kube-rbac-proxy/blob/master/.github/workflows/build.yml#L35-L42 to push the image to quay, however, to push the image to gcr.io/kubebuilder/kube-rbac-proxy |
Just to register. We need to use the latest version of |
@camilamacedo86 is there any update here ? |
Hi @hectorj2f, Unfortunately, I didn't have time to continue to see it. Would you like to help us with this one?
|
@camilamacedo86 I'd check what I can do ;), to speed things and get this done asap. |
just to register here: Why it is important we have the latest release for and update the kubebuilder scaffolds to use it as soon as possible? The latest images contain a fix brancz/kube-rbac-proxy#86 to make the images rootless to solve critical security concerns. More info: #1637. So, I am setting its milestone as 3.1.0. |
@hectorj2f did you get a chance to look into building the latest /cc @vincepri |
@estroz this is the task. Based on the meeting feel free to assign it to yourself. |
/assign |
Thanks @estroz |
my arm64 based k8s cluster complained that it could not detect platform in the manifest when pulling from |
I think our What's weird is |
thanks for looking into it @estroz . yeah, i see all four items in the manifest show |
EDIT: this is a red herring, @estroz is correct above in the source images being weird, but we prob still want to fix this eventually EDIT x2: the plot thickens Looks like
|
update: it turns out we weren't annotating the manifests properly (see above PR). IDK what's up with @estroz's docker though |
Per brancz/kube-rbac-proxy#99 (comment) has been pushed to quay.io/brancz/kube-rbac-proxy:v0.8.0. What is the process to update the gcr.io/kubebuilder/kube-rbac-proxy? Is this hand tagged and pushed by a maintainer?
Could you push it or retag it ? Thanks.
/kind bug
The text was updated successfully, but these errors were encountered: