K
Q

Jaeger-query and Jaeger-collector pods in CrashLoopBackOff

1/8/2020

I am trying to deploy the Jaeger Helm chart with Azure Cosmos DB acting as the Cassandra Storage Backend. I have set up the CosmosDB and created a values file as below:

storage:
  type: cassandra
  cassandra:
    host: xxxxxxx.cassandra.cosmos.azure.com
    port: 10350
    user: xxxxxx
    password: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    tls:
      enabled: false
      secretName: cassandra-tls-secret

provisionDataStore:
  cassandra: false

The command that I am using to deploy jaeger with the values file is:

helm install jaeger jaegertracing/jaeger -n <my-namespace> -f values.yml

However, on checking the pods, the collector and the query are in CrashLoopBackOff

enter image description here

Both the containers on running the describe command complain:

Readiness probe failed: HTTP probe failed with statuscode: 503

I am not sure what am I missing here?

-- Akash Masand
azure-cosmosdb
azure-kubernetes
cassandra
jaeger
kubernetes-helm

Similar Questions

Helm install in specific order for "deployment"
Kubernetes CentOS 8 tc command missing impact
Does Openshift "oc apply" overwrite the entire configuration or only the included parameters?
What is the best way to run a python process on a separate compute instance with Google Cloud Composer?

1 Answer

1/10/2020

Not sure, but it seems you miss setting the TLS for Cassandra Storage in Azure Cosmos DB. When you use the Cassandra client to connect the Cassandra Storage in Azure Cosmos DB, it will give out the time out error, but if you enable the SSL, the connection works well. So I think you can try to enable the TLS for Cassandra in your values.yaml following the steps in the Github which provided.

-- Charles Xu
Source: StackOverflow