Hello Yugabyte Community,
When you deploy the Yugabyte helm chart in a kubernetes cluster with istio sidecar injection enabled the setup-credentials-job never reaches “Complete” status. This is because even though the setup-credentials-job succeeds without issues, the istio sidecar in that pod keeps running. Kubernetes sees that the pod still has containers running in it and thinks the job is still running and never marks it as “Complete”.
This is an issue especially when using terraform to deploy the helm chart as the deployment of the helm chart times out and causes the terraform script to fail.
I have already created an issue about this on github ( Istio sidecars cause setup-credentials-job to never finish · Issue #206 · yugabyte/charts · GitHub ) with a proposed solution:
Explicitly shut down the sidecar at the end of the setup-credentials.sh script (optionally only do this if the script had no errors) with “curl -fsI -X POST http://localhost:15020/quitquitquit”. This works perfectly in other jobs that previously had exactly this issue.
I would really appreciate some feedback on this as this has been an issue for a while!