Kong reboot in DB-less mode
Answer
Configuring Kong on Kubernetes is done through Kubernetes native resources (e.g. Ingress) and Kong Custom Resources (e.g. KongConsumer, KongPlugin, KongIngress).
The Kong Ingress Controller will make all necessary changes based on changes to those resources through the Kubernetes API Server.
Additional Info
I highly recommend going through these guides. They are comprehensive and highly educational.
Make sure to keep an eye on the logs coming out of the Kong Ingress Controller pod because this will tell you whether it has successfully reconciled changes based on those resources or not.
Also feel free to take a look at this project where we manage Kong CRs through an on-cluster REST API Microservice.