🌱 Move kube-rbac-proxy into base manager yaml #695
Merged
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.
Description
Having
kube-rbac-proxy
in a separate patch makes working with manager args confusing. We either have to include all args into that patch (e.g. like--feature-gates=ForceSemverUpgradeConstraints=true
was added) or have a separate patch to override args.Since we have always have
kube-rbac-proxy
enabled anyway - why not move it into the base manager manifest?Reviewer Checklist