Added new ClusterRole and updated ClusterRoleBinding for RBAC #243
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
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.
📝 Description
Wanted to reduce the amount of RBAC permissions that are given to kube-monkey for security reasons. Currently, when RBAC is enabled through the Helm chart, kube-monkey is given permissions of the default Kubernetes ClusterRole
editwhich has quite extensive permissions over resources that kube-monkey does not need such as accessing secrets. Hence, this feature adds a new more restricted ClusterRole that only has thedeletepermission for pods, and only read permissions for Kubernetesapps(e.g. deployments).🔗 Related Issues
The following issue is quite old but was used as a starting point for how the ClusterRole could be configured with limited permissions: #22