Revert "Stop defaulting deprecated cdi.default in ClusterPolicy" - #2866
Revert "Stop defaulting deprecated cdi.default in ClusterPolicy"#2866tariq1890 wants to merge 1 commit into
Conversation
This reverts commit 62de6b5. Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
5c06bce to
8e53fab
Compare
📝 WalkthroughWalkthroughThe change adds a Kubernetes default of Merge Risk: 🟡 Moderate · up to This changes how omitted cdi.default values are materialized in ClusterPolicy resources, potentially affecting object shape and patch/apply behavior during upgrades. The compatibility impact should be justified or the marker reverted before merge. Comment |
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: 831e8d79-94b3-4b11-851d-dbe8c82b99af
⛔ 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; 9 remain after this review.
This reverts commit 62de6b5.
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