Open galsasi1989 opened 7 months ago
Agreed here. The post-install,post-upgrade
Helm hook should really map to the Sync
ArgoCD hook. In Helm the post-install,post-upgrade
happens after all the resources have been applied but not before they're up and healthy. This maps to the ArgoCD Sync
hook instead of the ArgoCD PostSync
hook which happens after the resources are applied and healthy.
Checklist:
argocd version
.Describe the bug
I am trying to deploy helm chart which contains a job with helm hook annotation: "helm.sh/hook: post-install,post-upgrade" When helm is used, the job is deployed successfully with the rest of chart's resources. But when the chart is deployed by argocd, the job is ignored. According to argocd documentation(https://argo-cd.readthedocs.io/en/stable/user-guide/helm/#helm-hooks) is seems like this helm annotation is translated into argocd hook annotation: "argocd.argoproj.io/hook: PostSync". According to the documentation about argocd PostSync hook(https://argo-cd.readthedocs.io/en/stable/user-guide/resource_hooks/) it seems like a different behavior: "Using a PostSync hook to run integration and health checks after a deployment.". So the behavior when the chart is deployed by argocd is different from the behavior when it's deployed by helm. The only solution I found is the use argo hook annotations instead those of helm but it's less preferred.
To Reproduce
Expected behavior
The job hook will be triggered by argo with the application workloads as done by helm when using the post-install,post-upgrade annotation.
Screenshots
Version
Logs