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
Hi, We have a kubernetes job defined in our application helm chart that is triggered by application postsync hook. If such job has a environment variables, we would expect ArgoCD to perform automatic sync when such environment variables are changed.
Observed state:
When environment variables are changed, ArgoCD autosync doesn’t happen (waited few hours). However if we run sync manually, job is run with new environment variables.
Is it expected ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, We have a kubernetes job defined in our application helm chart that is triggered by application postsync hook. If such job has a environment variables, we would expect ArgoCD to perform automatic sync when such environment variables are changed.
Observed state:
When environment variables are changed, ArgoCD autosync doesn’t happen (waited few hours). However if we run sync manually, job is run with new environment variables.
Is it expected ?
Beta Was this translation helpful? Give feedback.
All reactions