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 1 commit 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.
WalkthroughRemoved an empty Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
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.