+1 to Tims answer. Curious as to what are you trying to solve here ? Could you
explain your use case?
punit agrawal
dev-ops lead
new product development, ebay
On 8/10/18, 2:31 PM, "'Tim Hockin' via Kubernetes user discussion and Q&A"
<kubernetes-users@googlegroups.com> wrote:
Well, we're not "starting" the pods, we're queuing them up for when
nodes become available. Would you rather they get rejected
immediately? what if a node comes online 3 seconds after that
rejection?
On Fri, Aug 10, 2018 at 2:28 PM Basanta Kumar Panda
<pbasanta2...@gmail.com> wrote:
>
> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fgroup%2Fkubernetes-users&data=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777&sdata=XqT8%2BJyKObWAQQ83CWnPLAczjkaiamhK8%2BrVifpN%2B6g%3D&reserved=0.
> For more options, visit
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777&sdata=pUxWISpiOReuO8SUYZ7q7k0LXAqjJ%2B0gkbcptXWgsWc%3D&reserved=0.
--
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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fgroup%2Fkubernetes-users&data=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777&sdata=XqT8%2BJyKObWAQQ83CWnPLAczjkaiamhK8%2BrVifpN%2B6g%3D&reserved=0.
For more options, visit
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7Cpunagrawal%40ebay.com%7Cef2a3c8bbdb648b2e09608d5ff08a07a%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636695334903045777&sdata=pUxWISpiOReuO8SUYZ7q7k0LXAqjJ%2B0gkbcptXWgsWc%3D&reserved=0.
--
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.
