chore: drop legacy capabilities.backend-storage support - #919
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe chart now enables backend storage only through ChangesBackend storage capability deprecation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The chart now rejects the removed backend-storage capability and uses node-agent configuration for backend storage enablement. Existing deprecated enabled configurations will receive a clear render-time migration error; no current merge-blocking risk is identified. Suggested reviewers: 🚥 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 |
Remove fallback to capabilities.backend-storage enable in configurations and clean up obsolete tests. Bump chart version to 1.40.5. Signed-off-by: Matthias Bertschy <matthias.bertschy@gmail.com>
3cd1a27 to
2400870
Compare
Overview
Drops the legacy fallback to
capabilities.backend-storage: enablein_common.tpl.Following the refactoring in #884 where
nodeAgent.config.extra.backendStorageEnabledwas introduced, this PR cleans up the upstream chart by:else if eq (index .Values.capabilities "backend-storage" | default "") "enable"in theconfigurationstemplate.malware_capability_gate_test.yaml.How to Test
Run helm unit tests:
Checklist before requesting a review