We are using Kong in Db less mode along with Kong Ingress controller. We use custom config templates for both kong and nginx. To keep the connection secure, we also provide our ssl certificates to the following configuration fields in the respective files:
ssl_cert = /etc/secret-volume/ssh-publickey ssl_cert_key = /etc/secret-volume/ssh-privatekey
ssl_certificate /etc/secret-volume/ssh-cluster-publickey; ssl_certificate_key /etc/secret-volume/ssh-cluster-privatekey
We have use case to upload new certificates while the system is online. If we do a soft reload of kong using “kong reload”, it is losing the routes/services info from kong instance till the kong ingress controller container is restarted.
Is there any other better approach to do soft restart such that the new certificates get used?
Thanks for your help!