Do not generate empty required arrays in OneOf definition #10492
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.
Type of change
Description
Currently, we generate empty
required
arrays in theOneOf
definitions in the CRDs. That seems to cause issues to some tools that do the diffing of the CRDs as Kubernetes seems to remove the empty arrays (see https://cloud-native.slack.com/archives/CMH3Q3SNP/p1724662526753129 as an example).This PR adds a check and generates the arrays only if they have any values. This is what we already do for the
required
arrays in other places, so it should hopefully not cause any issues.Checklist