Redis-cluster Helm chart unable to complete job when using istio

Question

When using the Bitnami Helm chart for Redis-Cluster, there is a redis-cluster-cluster-create job. However, when enabling istio-injection, this job never ends. If I disable istio-injection, the job quickly ends. Any solutions or reason why this phenomenon is happening?

Answer 1

Answering the main question

there is a redis-cluster-cluster-create job. However, when enabling istio-injection, this job never ends. If I disable istio-injection, the job quickly ends. Any solutions or reason why this phenomenon is happening?

The main issue here is that job is not considered complete until all containers have stopped running, and Istio sidecar run indefinitely, while your task may have completed, the Job as a whole will not appear as completed in Kubernetes.

There is github issue about that.

There is one of the workarounds, and you can find more workarounds here.

---

I can change the podAnnotations from Redis-Cluster Helm Chart, and when disabling the istio-injection, the Job doesn't spin up istio-proxy. However, the main job 'cluster-create' job never ends, and eventually fails the the deploy

As mentioned here

So as a temporary workaround adding sidecar.istio.io/inject: “false” is possible but this disables Istio for any traffic to/from the annotated Pod. As mentioned, we leveraged Kubernetes Jobs for Integration Testing, which meant some tests may need to access the service mesh. Disabling Istio essentially means breaking routing — a show stopper.

So it might actually not work here. I suggest to try with the quitquitquit as it's the most recommended workaround.

---

Additionally worth to check these github issues:

• List of applications incompatible with Istio
• helm stable/redis does not work with istio sidecar
• Using Istio with CronJobs
• Sidecar Containers