feat: remove empty properties from etcd-cluster spec to avoid ArgoCD drifting#301
feat: remove empty properties from etcd-cluster spec to avoid ArgoCD drifting#301apenen wants to merge 2 commits intoaenix-io:mainfrom
Conversation
…drifting ArgoCD keeps detecting pending changes because Kubernetes omits empty fields on apply. Removing these fields from the spec prevents unnecessary diffs.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughRemoved an empty Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
|
Hi, @apenen! This change will be overriden by commands make manifests
make helm-crd-copySo changes need to be made to |
ArgoCD keeps detecting pending changes because Kubernetes omits empty fields on apply. Removing these fields from the spec prevents unnecessary diffs.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.