Temporal Helm Cassandra problem

Hi all!

We are trying to install temporal server and all the related components on Kubernetes using Helm and the values.yaml here attached (https://we.tl/t-vFfB2DvN8J).
Unfortunately the entire stack does not get ready probably due to error in cassandra. The error we get is “waiting for default keyspace to become ready”, even if Cassandra is up and running.
Any advice on this problem?

Thank you very much!
A.

How are you creating the schema needed by Temporal?

Make sure schema is created before the Temporal server comes up.

the helm chart should run some batch jobs that set up the schema in the helm chart - helm-charts/server-job.yaml at master · temporalio/helm-charts · GitHub

it does look like replicationFactor is set correcetly - can you look at the logs for the job and make sure the keyspace was created with rf 1 (and that the job ran to create the schema).

the error you are getting happens after the deployment verifies that cassandra is alive but while it’s waiting for the keyspace - helm-charts/server-deployment.yaml at master · temporalio/helm-charts · GitHub

hopefully that will help point in the right direction, but please let us know if you need any other help!

Thank you very much @derek and @samar.
Can you give me an example of the values.yaml file that can correctly initialize temporal with just cassandra?