ybudweiser opened a new issue, #23940:
URL: https://github.com/apache/superset/issues/23940
When deploying the superset helm chart via argo cd - the init-db job is not
executed and not the job resource is not either created in kubernetes.
#### How to reproduce the bug
1. Create an argo application manifest to deploy superset chart
2. monitor the deployment progress
### Expected results
argo cd generates the correct job resource
### Actual results
The 3 K8 deployments are generated and pods start up. These pod enter a
crashrestart loop because the database was never initialized.
The init-db job is never generated by argo and not executed.
#### Screenshots
If applicable, add screenshots to help explain your problem.
### Environment
(please complete the following information):
- superset version: `2.1.0`
- helm chart: 0.9.1
### Checklist
Make sure to follow these steps before submitting your issue - thank you!
- [ *] I have reproduced the issue with at least the latest released version
of superset.
- [ *] I have checked the issue tracker for the same issue and I haven't
found one similar.
### Additional context
Root cause here is how arogcd maps the helm hooks to the argo lifecycle. The
helm job is annotated with
```
"helm.sh/hook": post-install,post-upgrade
"helm.sh/hook-delete-policy": "before-hook-creation"
```
This maps to argocd's postsync hook and requires argo to run the init-db job
only after the main sync phase has completed successfully and the pods are
healthy. However, in our case the pods wont become healthy without running the
init-db job first.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
