KONG API INSTALLATION FAILURE DUE TO CASSANDRA CONFIG
We have Kong API running on Kubernetes. It uses Cassandra to store meta data. The setup used in production is clustered one but due to cost consideration we were asked to build a POC environment with single node. We were given two VMs – one to run Kubernetes control plane and other to run Cassandra and Kong worker nodes. As you are aware there are 3 basic steps to install Kong API: 1) Create and run Cassandra pods. 2) Run Kong migrations to create Kong data schemas in Cassandra. 3) Create and run Kong pods. We made necessary changes in values.yaml of helm charts of Cassandra and Kong to reflect new environment. When we ran Helm charts Cassandra DB and Kong migrations got created successfully but Kong pods were stuck in Init state. Kong pod had two containers: wait-for-db and Kong containers. wait-for-db container had been stuck so pod also stuck in Init state. We looked at this init container using following command: kubectl logs <kong pod> -c wait-for-db T...