configMap volume mount failure

Asked Jul 05 '20 at 13:06

Active Jul 05 '20 at 13:06

Viewed 3,611 times

I've got a question, guys.

Any idea what would cause this sort of error.

MountVolume.SetUp failed for volume "PNIF-uid" : failed to sync configmap cache: timed out waiting for the condition.

The pod doesn't crash-loop by the way, which is what I expect to happen if one of the containers is unable to mount a configMap volume.

asked Jul 05 '20 at 13:06

Hammed

is it minikube or kubeadm or something else? – Arghya Sadhu Jul 05 '20 at 13:19
It's with Kubeadm. Trying to mount the configMap as a volume and I get this warning when I run the kubectl describe pod command. – Hammed Jul 05 '20 at 13:39
How is your API Server doing..any sign of heavy load? – Arghya Sadhu Jul 05 '20 at 13:41
Could a lot of load on the API server be responsible for this? How do you determine how much load the API server might be under anyway? – Hammed Jul 05 '20 at 13:48
you can check the API Server metrics exposed..a prometheus alert can be more helpful – Arghya Sadhu Jul 05 '20 at 14:07
Can you please share your YAML file so that it will be easy to understand the problem for others. – Himadri Ganguly Jul 05 '20 at 15:46
Hi, what is You cluster setup like? What k8s version how many master/worker nodes etc. – Piotr Malec Jul 06 '20 at 14:52
Would be helpful if you add more details. – Tek Nath Acharya Jul 06 '20 at 15:53
I am currently having the exact same issue here – Elouan Keryell-Even Sep 17 '21 at 08:56

0 Answers0