Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Kube-scheduler doesn't retry rescheduling the pod #87145
What happened: Pod remains in a Pending state. In the kubernetes yaml file we have one daemonSet, one PV and one PVC to be created. Daemonset pods are using the PVC. Deleting and recreating these resources in a loop creates this issue intermittently. Even in success case in the events section I do see few initial warning messages "pod has unbound immediate PersistentVolumeClaims" where scheduling fails which is expected as PVC , PV and pods are being created at same time but after few retries, it succeeds. But sometimes pod stucks in "Pending" state forever unless kube-scheduler is restarted.
Warning FailedScheduling 28m (x2 over 28m) default-scheduler pod has unbound immediate PersistentVolumeClaims
x2 count remains the same.
What you expected to happen: Kube-scheduler should retry scheduling and pod status should be changed to Running.
How to reproduce it (as minimally and precisely as possible): Deleting and re-creating the resources using the yaml file in loop using a shell file.
Anything else we need to know?: Kubernetes cluster is running in HA mode.