Allow disabling the installation of starboard CRDs when starboard is enabled #887
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
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.
Summary
Introduce a new option that allows users to disable the installation of starboard CRDs when starboard is enabled.
Context
Starboard installs a set of Custom Resource Definitions that are necessary for its operations. However, in some scenarios, users may prefer not to install these CRDs, either due to pre-existing configurations or specific deployment requirements.
This PR might solve this issue: #885
To address this, a new configuration option should be added, allowing users to disable the automatic installation of starboard CRDs while still enabling starboard itself. This enhancement will give users greater flexibility and control over their Kubernetes environment, ensuring that Starboard can be used in a wider range of deployment scenarios without unnecessary overhead or conflicts.
Changes Made
Testing
Manually tested the deployment of kube-enforcer using Minikube and the Helm chart with
starboard.crdsdisabled.