Is there any other way to update configmap for deployment without pod

1.	Is there any other way to update configmap for deployment without pod restarts?
Answer» well you need to have some way of triggering the RELOAD. ether 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. 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

Is there any other way to update configmap for deployment without pod restarts?

Answer»

well you need to have some way of triggering the RELOAD. ether 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. 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

Discussion

No Comment Found

Related InterviewSolutions

If you have a pod that is using a ConfigMap which you updated, and you want the container to be updated with those changes, what should you do?
When deploying you will get an error of mounting as read-only, which is effecting to fluent to read some of the mentioned sources in the configmap.how can we avoid this read-only error?
volumeMounts:name: fluentdmountPath: /fluentd/etcname: varlogmountPath: /var/logname: container1mountPath: /var/lib/docker/containersreadOnly: truesecurityContext:privileged: trueterminationGracePeriodSeconds: 30volumes:name: varloghostPath:path: /var/logname: container1hostPath:path: /var/lib/docker/containersname: fluentdconfigMap:name: fluentd-config
I have a configmap for 3 files that are going to be mounted in supposing "fluentd/etc/" and the respective files would be fluent.conf, kubernetes.conf, systemd.conf, config map in deployment.yaml is like this
How to configure a default ImagePullSecret for any deployment?
How should you connect an app pod with a database pod?
Does the container restart When applying/updating the secret object (kubectl apply -f mysecret.yml)? If not, how is the new password applied to the database?
How service that selects apps based on the label and has an externalIP?
What is the impact of upgrading kubelet if we leave the pods on the worker node - will it break running pods? why?
If I have multiple containers running inside a pod, and I want to wait for a specific container to start before starting another one.