If you are mounting the secret as a volume into your pod, when the secret is updated the content will be updated in your pod, without the pod restarting.
It's up to your application to detect that change and reload, or to write your own logic that rolls the pods if the secret changes.
volumeMount controls what part of the secret volume is mounted into a particular container (defaults to the root, containing all those files, but can point to a specific file using `subPath`), and where in the container it should be mounted with `mountPath`.
Example spec :
- readOnly: true
- name: server-cert
Also, it depends on how the secret is consumed by a 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 secret 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
The application must return a 200 status ...READ MORE
Make sure that your pod yaml file ...READ MORE
You cannot achieve this in kubernetes pod. ...READ MORE
When a node is tainted, the pods ...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
You could use kubectl get deployment <deployment>.
If ...READ MORE
By default, anti-affinity is not attempted by ...READ MORE