We are using configmaps as a way to store configuration data for our pods. At startup these configmaps are mounted as configuration files inside the container.
Unfortunately an update of a configmap will not be picked up by ASP.NET Core.
A way to solve this is by explicitly triggering a new deployment afterwards:
kubectl rollout restart deploy/example-api-deployment
I created another(better?) approach but that is for another blog post…
No comments:
Post a Comment