CU-86c0fwhr0 - feat: allow not creating rbac at all #334
+5
−1
Conversation
This file contains 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
|
Opened a new task on ClickUp! |
komodor-github-warden
bot
changed the title
|
Task linked: CU-86c0fwhr0 feat: allow not creating rbac at all |
Moran-k
approved these changes
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Some accounts have security policies that require teams to validate changes in Kubernetes RBAC. By not creating RBAC, the Helm chart will avoid generating any cluster roles or bindings. However, modifying RBAC places full responsibility on the account for managing permission errors, which can lead to unexpected behavior. This approach is not recommended and should be used with caution.