@hbagdi, Thank you so much for the quick response. If it is stored in memory, what is the best way to handle kong reload? Earlier, we had been using kong with Cassandra db (without ingress controller) and now we are moving to Kong ingress controller + db less mode. We also use custom nginx templates.
So our kong reload has been using the following command:
kong reload --conf /etc/kong/kong.conf --nginx-conf /etc/kong/kong_nginx.conf --vv
When I run reload on dbless, the routes are being lost as it complains with error
“message”: “no Route matched with those values”
This issue is not seen when I restart kong though!
Also, we had been writing custom plugins and also extended admin api (implemented api.lua), will this still work with this dbless config + kong ingress controller deployment?
Any pointers to how this can be resolved will be very helpful.