If you have faced the following problem (see the screenshot), then you know probably the specific node where the persistent volume resides is not working properly and more specifically the kubelet is not working properly!
So, I would suggest the following two actions:
- Check the Volume Attachments more details can be found in the following link: veducate.co.uk/kubelet-unable-attach-volumes
See also the Google Documentation how to add a new node to the nodepool cloud.google.com/kubernetes-engine/docs/how..
- Add a new node in the nodepool and drain the problematic one!
kubectl drain <node-name> --ignore daemonsets -- delete-emptydir-data
I hope you like the tutorial, if you do give a thumps up! and follow me in Twitter, also you can subscribe to my Newsletter in order to avoid missing any of the upcoming tutorials.
Media Attribution
I would like to thank Clark Tibbs for designing the awesome photo I am using in my posts.