Hello,
I am encountering an issue during the deployment of Zammad on Kubernetes. The initialization job fails because Elasticsearch takes too long to start. This delay prevents the initialization process from completing successfully.
- Used Zammad version: 6.4.1
- Used Zammad installation type: k8s, official image
- Operating system: debian
- Browser + version: vivaldi 7.0.3495.29
Expected behavior:
- Zammad initializes successfully during deployment, with the init job completing without errors.
- Elasticsearch starts in a timely manner and becomes available before the Zammad initialization process begins.
Actual behavior:
- The Zammad initialization job fails due to Elasticsearch being slow to start.
- Logs indicate a timeout or failure to connect to Elasticsearch during the initialization process.
Steps to reproduce the behavior:
- Deploy Zammad on Kubernetes using [Helm/custom manifests, specify method].
- Configure Elasticsearch as a required dependency within the same deployment.
- Deploy the stack and monitor the logs of the Zammad init job.
- Observe that the job fails due to the unavailability of Elasticsearch.