Repository navigation
fix(cdi): drop the ExpandDisks gate from the CDI object - #4415
Conversation
ExpandDisks is a KubeVirt feature gate. CDI declares no gate by that name and matches gate names exactly, so the entry was accepted and ignored. Disk expansion is a KubeVirt feature, GA there at the release the platform ships, so listing the gate on the CDI object points a reader tracing where expansion comes from at the wrong component. The feature-gate list is pinned whole in its own case, so a gate added beside the one upstream ships turns the suite red. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <[email protected]>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: cozystack/cozystack/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 WalkthroughWalkthroughThe CDI custom resource no longer lists ChangesCDI feature gate configuration
Merge Risk: ⚪ Minimal · up to The CDI configuration now lists only its remaining gate, with a test protecting that list. No merge-blocking issue is identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What this PR does
This drops a feature gate from the CDI object that CDI never reads.
ExpandDiskssits inspec.config.featureGatesinpackages/system/kubevirt-cdi/templates/cdi-cr.yaml, but it is a KubeVirt gate.CDI v1.66.1 has no gate with that name. It looks a gate up by exact name, so an extra entry is read and ignored. The CRD types the list as plain strings, so nothing rejects it either. Disk expansion comes from KubeVirt, where
ExpandDisksis GA at v1.9.0, the release the platform ships. I left the KubeVirt CR as is; #4029 tracks the GA gates in that list.The gate list now has its own test case, pinned whole to what upstream's
cdi-cr.yamlships. AddingExpandDisksback turns it red.make updateonly checks the upstream file against its pinned hash and writes nothing undertemplates/, so it can't bring the line back.Closes #4112
Screenshots
No UI change.
Downstream repositories
Release note
Summary by CodeRabbit
HonorWaitForFirstConsumerfeature gate. TheExpandDisksgate is no longer included in the configuration.