[mayfly] Support custom ClusterRole rules through values.yaml #32
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
This PR enhances the Mayfly Helm chart by adding the capability to customize the ClusterRole rules directly through the values.yaml file. This provides better flexibility for users to define their own RBAC permissions without having to modify the template files.
I've seen that it's possible to limit the resources that the operator will manage, but it's probably better to restrict rights directly from the Kubernetes RBAC by editing the clusterRole.
Example Usage
Users can now customize the ClusterRole permissions by adding their specific rules in the values.yaml file: