Revert "Stop defaulting deprecated cdi.default in ClusterPolicy" - #2865
Revert "Stop defaulting deprecated cdi.default in ClusterPolicy"#2865tariq1890 wants to merge 1 commit into
Conversation
This reverts commit 2346486. Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
76cc1ef to
4fa1eda
Compare
📝 WalkthroughWalkthroughThe change adds a Kubernetes Merge Risk: ⚪ Minimal · up to This restores the deprecated CDI field’s prior false default and updates the distributed CRD manifests consistently. No merge-blocking product risk is currently evident. Comment |
|
Closing as this Revert PR targets the cherrypick commit as opposed to the original commit. |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: QUIET
Plan: Enterprise
Run ID: ac6158e7-513a-4066-a63d-6c8881964c72
⛔ Files ignored due to path filters (3)
bundle/manifests/nvidia.com_clusterpolicies.yamlis excluded by!bundle/manifests/nvidia.com_*.yamlconfig/crd/bases/nvidia.com_clusterpolicies.yamlis excluded by!config/crd/bases/**deployments/gpu-operator/crds/nvidia.com_clusterpolicies.yamlis excluded by!deployments/gpu-operator/crds/**
📒 Files selected for processing (1)
api/nvidia/v1/clusterpolicy_types.go
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review.
|
|
||
| // Deprecated: This field is no longer used. Setting cdi.enabled=true will configure CDI as the default mechanism for making GPUs accessible to containers. | ||
| // +kubebuilder:validation:Optional | ||
| // +kubebuilder:default=false |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Regenerate and justify this released CRD change before merging.
Line 1970 changes the default for an existing ClusterPolicy field. After the generated CRD is applied, requests that omit spec.cdi.default can persist false. The deprecated field is not used by CDIConfigSpec.IsEnabled(), so this can change stored objects and ArgoCD diffs without changing CDI runtime behavior.
The cohort includes only api/nvidia/v1/clusterpolicy_types.go. Regenerate and commit the CRD assets and deepcopy output required by this API-type change. Document why the changed default is safe for already-applied ClusterPolicy resources.
As per path instructions, api/**/*.go contains released CRDs; changed +kubebuilder:default values are major API changes, and editing these types requires regenerated deepcopy and CRD assets.
Source: Path instructions
This reverts commit 2346486.
server-side diff strategyin ArgoCD fixes the issue for Argo users who face this problem. That is a better solution than making an upstream CRD schema change