fix: add kubebuilder markers for non-breaking kube-api-linter issues #2654
+88
−39
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.
#2419
Summary
This PR addresses non-breaking kube-api-linter issues identified in #2618 by adding appropriate kubebuilder markers to API field definitions.
Changes
Added kubebuilder markers:
+listType=atomictoTaints,StartupTaints,Requirements, andBudgets+listType=settoReasons(no duplicates allowed)+listType=mapwith+listMapKey=typetoConditions(indexed by type)+mapType=atomictoLabels+mapType=granulartoAnnotationsRetained
//nolint:kubeapilinterfor:metav1.ObjectMeta,Status, etc.)*NodeClassReference,*metav1.Duration, etc.)Testing
All changes are non-breaking and only add metadata markers that don't affect runtime behavior or API compatibility.
Related to #2618