Describe the bug
ArgoCD reports a difference in the live manifest and the manifest generated by https://github.com/aaronsgithub/homelab/tree/965f4fe88f99115e742c0485ab0b966c142db75b/appsets/system/vault, giving an OutOfSync status.
Expected behavior
We either want to have the status showing as syncrhonized or have ArgoCD ignore expected mutations of the manifest after deployment.
Current behavior
- A PersistentVolumeClaim named data-vault-0 is produced in the Live manifest but is absent from the desired manifest
- A caBundle is added to the MutatingWebhookConfiguration vault-agent-injector-cfg in the live manifest, which does not appear in the desired manifest.
To reproduce
See https://github.com/aaronsgithub/homelab/tree/965f4fe88f99115e742c0485ab0b966c142db75b/appsets/system/vault
Possible Solutions
- Get ArgoCD to ignore the diff of the caBundle
- Understand why the PersistentVolumeClaim is absent from the desired manifest, find out if this is expected behaviour, and get ArgoCD to ignore this difference too.
See https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/
Describe the bug
ArgoCD reports a difference in the live manifest and the manifest generated by https://github.com/aaronsgithub/homelab/tree/965f4fe88f99115e742c0485ab0b966c142db75b/appsets/system/vault, giving an OutOfSync status.
Expected behavior
We either want to have the status showing as syncrhonized or have ArgoCD ignore expected mutations of the manifest after deployment.
Current behavior
To reproduce
See https://github.com/aaronsgithub/homelab/tree/965f4fe88f99115e742c0485ab0b966c142db75b/appsets/system/vault
Possible Solutions
See https://argo-cd.readthedocs.io/en/stable/user-guide/diffing/