fix: add default managementState as Removed to allow new components to show up in old DSCs, fixes RHOAIENG-14194 #1293
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
Add default managementState as Removed to allow new components to show up in old DSCs
Without the default managementState, K8s apiserver uses an empty component object with unspecified management state. Even though the operator treats that as Removed, it's better to have that specified explicitly as the default value in the CRD.
Fixes RHOAIENG-14194
How Has This Been Tested?
Tested manually by manually removing a component from a CRD, putting it back but with a default managementState value in the CRD.
To test it manually by temporarily removing the modelmeshserving component and adding it back again, try the commands:
Screenshot or short clip
Merge criteria