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,
I use your helm chart, version 1.33.1. I use argocd to manage my kubernetes cluster
The job haproxy-ingress-private-crdjob-1 that is created has a ttlSecondAfterFinish, which will completely delete the job after 120 seconds. This causes an issue with Argo's synchronization as it immediately goes out of sync.
How can I resolve this problem so that my application can return to a Healthy status?
The text was updated successfully, but these errors were encountered:
The bug is in ArgoCD and while we understand that this might be a blocker for you, we have strong reasons for not using hooks due to compatibility with systems that don't use Hooks (such as AWS Container Marketplace). You should implore ArgoCD team to fix the issue.
Hi,
I use your helm chart, version 1.33.1. I use argocd to manage my kubernetes cluster
The job haproxy-ingress-private-crdjob-1 that is created has a ttlSecondAfterFinish, which will completely delete the job after 120 seconds. This causes an issue with Argo's synchronization as it immediately goes out of sync.
How can I resolve this problem so that my application can return to a Healthy status?
The text was updated successfully, but these errors were encountered: