You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using a custom sync label for ArgoCD (e.g argocd.argoproj.io/instance as per the official recommendation here), then the app stays out-of-sync in ArgoCD, without any actual diff being reported.
Looking then at the manifests being provisioned, the argocd.argoproj.io/instance label is missing entirely. So, AFAICT, there seems to be a very weird behaviour with that chart in particular that prevent ArgoCD from injecting the label.
For the record, we have over 30 apps running on our cluster in a very consistent way with the same overall config, and vault is the only one showing the weird behaviour.
Describe the bug
When using a custom sync label for ArgoCD (e.g
argocd.argoproj.io/instance
as per the official recommendation here), then the app staysout-of-sync
in ArgoCD, without any actual diff being reported.Looking then at the manifests being provisioned, the
argocd.argoproj.io/instance
label is missing entirely. So, AFAICT, there seems to be a very weird behaviour with that chart in particular that prevent ArgoCD from injecting the label.For the record, we have over 30 apps running on our cluster in a very consistent way with the same overall config, and
vault
is the only one showing the weird behaviour.To Reproduce
Steps to reproduce the behavior:
application.instanceLabelKey: argocd.argoproj.io/instance
Out-of-sync
in ArgoCDvault-0
manifest (argocd.argoproj.io/instance
is missing):Other useful info to include: vault pod logs,
kubectl describe statefulset vault
andkubectl get statefulset vault -o yaml
outputExpected behavior
Environment
0.28.0
Chart values:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: