fix: remove rbac Secrets from app rules #4203
Open
Conversation
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
Be able to watch flux resources in UI without having rights to read secrets in k8s.
|
@DanielAntos90 what is the reason for this change? |
|
@casibbald the reason for this change is that, in our setup, developers lack permissions to access secrets due to security policies. Without this adjustment, developers are unable to observe or even manage (e.g., halt reconciliation) any objects (Kustomization or HelmRelease) controlled by Flux. Restrictions on the Weave side prevent developers from viewing these objects in the UI, leaving them with no visibility at all. |
|
@DanielAntos90 Drop me a PM to connect up on this. |
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.
Be able to watch flux resources in UI without having rights to read secrets in k8s.