I often destroy and redeploy a cluster.
For the initial launch, I do the following:
- build a new cluster
- deploy an empty postgresql db
- deploy kong-ingress-controller
- execute kong migrate bootstrap
To create a new Kong Consumer, I create a new KongConsumer k8s object which will create a new consumer entry in kong postgresql db.
Then, I do the following:
- save my postgresql kong db
- destroy my cluster
- rebuilding a new cluster
- deploy postgresql db
- import saved postgresql kong db
- deploy kong-ingress-controller
- execute kong migrate bootstrap
I notice that all the KongConsumer that I have created in my initial deployment no longer exists when I redeploy to a new cluster. I was under the assumption that kong-ingress-controller would automatically recreate a KongConsumer object for each consumer that do not already exists in the current kubernetes state but do exists in the postgresql kong db.
Question:
If a consumer make a request to the api gateway and this consumer exists in the postgresql kong db but not as a k8s object, will kong-ingress-controller still recognize it ?