Well, you need to have some way of triggering the reload.
Either do a check every minute or have a reload endpoint for an API or project the configmap as a volume, could use inotify to be aware of the change.
It depends on how the configmap is consumed by the container. If env vars, then no. If a volumeMount, then the file is updated in the container ready to be consumed by the service but it needs to reload the file.
The container does not restart. if the configmap is mounted as a volume it is updated dynamically. if it is an environment variable it stays as the old value until the container is restarted.volume mount the configmap into the pod, the projected file is updated periodically. NOT realtime. then have the app recognise if the config on disk has changed and reload.
When a node is tainted, the pods ...READ MORE
You can create a simple job based ...READ MORE
You could use kubectl get deployment <deployment>.
If ...READ MORE
By default, anti-affinity is not attempted by ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Try using ingress itself in this manner
except ...READ MORE
Hi Kalgi after following above steps it ...READ MORE
Follow these steps:
$ kubeadm reset
$ kubeadm init ...READ MORE
Yes using replication controller but it may ...READ MORE
Yes, it is possible for containers to ...READ MORE