Hi , Here is one of the Scenario 1. K8S Master is up with 2 slave nodes and is configured to jenkins master. 2. Both the slave nodes are down. 3. Job triggered from jenkins and the job is waiting/hanging.
bash-4.2kubectl get nodes NAME STATUS ROLES AGE VERSION Server1 Ready,SchedulingDisabled <none> 34d v1.9.1+2.1.5.el7 Server2 Ready,SchedulingDisabled <none> 29d v1.9.1+2.1.5.el7 Server3 Ready,SchedulingDisabled master 34d v1.9.1+2.1.5.el7 bash-4.2$ kubectl get pods -o wide -w NAME READY STATUS RESTARTS AGE IP NODE kube-lv7dz 0/1 Pending 0 0s <none> <none> kube-lv7dz 0/1 Pending 0 0s <none> <none> kube-lv7dz 0/1 Terminating 0 4m <none> <none> kube-lv7dz 0/1 Terminating 0 4m <none> <none> kube-7mztq 0/1 Pending 0 0s <none> <none> kube-7mztq 0/1 Pending 0 0s <none> <none> Here pods are waiting to be scheduled on the slave nodes and since no slave nodes are available, jobs are waiting/hanging. is there a way to not start the pod creation as no nodes available to run the jobs ? Regards, Basanta -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
