[bitnami/rabbitmq-cluster-operator] Add AdmissionWebhookConfig toggle #28801
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 of the change
This PR proposes a new toggle to allow users to skip creation of
AdmissionWebhookConfig
resource.Benefits
This toggle can be useful for when users have restricted cluster-wide permissions and are only allowed to deploy namespaced scope resources.
Possible drawbacks
The only drawback is the fact that users would have to manually create the
AdmissionWebhookConfig
by themselves.Applicable issues
Additional information
Since the default value for the toggle is set to
false
we would keep compatibility with the current behaviour, without risking a breaking change for users that are unaware or don't require the use of this toggle -- only users who explicitly opt-in would make use of it.Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm