I have deployed kong with cassandra using the helm chart : https://github.com/helm/charts/blob/master/stable/kong/values.yaml with tweaks to replace postgre with cassandra database
Kong and Cassandra came up fine. However, I noticed it took Kong 5 crashes before coming up, and after deploying and deleting couple of times, I see that cassandra intanaces (3) are taking a while to initialize, causing Kong to crash until all three instances are initialized.
[vagrant@localhost cgbu-nrf-cne] kubectl get pods NAME READY STATUS RESTARTS AGE csr-kong-cassandra-0 1/1 Running 0 12h csr-kong-cassandra-1 1/1 Running 0 12h csr-kong-cassandra-2 1/1 Running 0 12h csr-kong-kong-85cf4859cb-lwflk 1/1 Running **_5_** 12h csr-kong-kong-migrations-77nzc 0/1 Completed **_5_** 12h [vagrant@localhost cgbu-nrf-cne]
My question: How do I keep kong from coming up until required cassandra instances are initialized?