Migration of kube-rbac-proxy in argo-rollouts-manager#133
Merged
jgwest merged 1 commit intoApr 16, 2026
Conversation
Signed-off-by: akhil nittala <nakhil@redhat.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do / why we need it:
(Provide a list of the changes you have made, and why you made those changes)
(You don't need to re-mention any changes/reasons which are already documented in the issue)
Since kube-rbac-proxy has been officially deprecated and removed from the GCR repository, we are eliminating this image dependency by transitioning to the controller-runtime’s built-in functionality.
Have you updated the necessary documentation?
Which issue(s) this PR fixes:
Fixes #?
https://redhat.atlassian.net/browse/GITOPS-9257
How to test changes / Special notes to the reviewer:
Install argocd rollouts operator with this changes and verify argocd rollouts operator now has only one container created, but metrics should be there as it is without impacting argocd rollouts operator metrics functionality.