Kubernetes Secret management

Asking for help? Comment out what you need so we can get more information to help you!

Cluster information:

Kubernetes version:v1.14.6
Cloud being used: bare-metal
Installation method:VmWare
Host OS: Ubuntu
CNI and version:Calico 18.09.9
CRI and version:

Hi All,
Secrete keys volume mounted on POD causes following behavior -

  • add/delete of a secret causes restart
  • modify of secret update on pod without restart

Is there a way secrete add/delete avoids a POD restart? Additionally, what is the recommended behavior for secrete mgmt?


If add and delete always requires POD restart due to contract of mounting volume first and then deploying containers. Then is it a better practice to perform POD restart for updates too which decouples POD application from implementing secret mgmt logic in application.