HPA kills new pods instantly after creation about helm HOT 5 CLOSED

Additional information:
The problem seems to be in ArgoCD. When disabling the self-heal option, all replicas are scheduled as exepted.

I suspect that ArgoCD detects a diff in the deployment.yml (replicas: 1 != replicas: 3) and then adjusts this again. So removing the replicas option when HPA is enabled could really be the solution.

from helm.

@lorrx thanks for issue and the updates 🙏 , if you have found a solution that works both in Argo CD and via helm directly on a k8s cluster, please feel free to submit a PR to correct the issue.

from helm.

@lorrx if you can, could you try pointing your Argo CD Application (or ApplicationSet) at my fix/dont-set-replicas-in-pod-if-hpa-enabled branch?

Sorry if I'm over-explaining, but just in case you need the info, it would be something like this for your source:

      source:
        repoURL: 'https://github.com/jessebot/nextcloud-helm'
        targetRevision: fix/dont-set-replicas-in-pod-if-hpa-enabled
        path: charts/nextcloud/

If you're using an Argo Project, then you'll also need to add https://github.com/jessebot/nextcloud-helm as an allowed source repo. Let me know if this works for you and we can work on getting that PR merged 🙏 Thanks!

from helm.

update: I think we're actually good to merge the above PR based on #596 (comment), which would auto-close this Issue. If that happens, and it's still broken, we can absolutely re-open this Issue, or you can open a second one. Either way, happy to help :)

from helm.