OPENSTACK-HELM : INGRESS CONTROLLER PODS STUCK IN PENDING

Akki yadav yadav.akshay58 at gmail.com
Wed May 29 05:24:16 UTC 2019


Hello team,
    I am running the following command in order to deploy the ingress
controller:
    - ./tools/deployment/multinode/020-ingress.sh
It makes two pods ingress-error-pages-899888c7-pnxhv and
ingress-error-pages-899888c7-w5d5b which remains in pending state and the
script ends after 900 seconds stating in "kubectl describe" that :
    - Warning  FailedScheduling  60s (x3 over
2m12s)  default-scheduler  0/3 nodes are available: 3 node(s) didn't match
node selector.

As only default labels are associated with the cluster nodes, do i need to
add any specific one ? If yes, Please tell me where and how to add the same.

Please guide me how to resolve this issue.
Thanks in advance.

Regards,
Akshay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190529/365658f3/attachment-0001.html>


More information about the openstack-discuss mailing list