Config follow-up: Implement component override functionality for Config resource #475
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.
This commit adds the ability to mark components as unmanaged in the
bpfman-operator, preventing the operator from creating or updating
specific objects. The implementation includes:
kind, group, namespace, name, and unmanaged flag
management of unmanaged components
override specifications
across all component types
Documentation
This will need documentation that states how to generate the overrides, e.g. (generated with an LLM, lgtm but haven't had the time to retest the below combinations, yet):
Using JSON patch for more precise control:
The /- notation appends to the existing overrides array rather than replacing it.