nginx-ingress-controller 启动不了一直Pending

来源：6-6 部署ingress-nginx（下）

847206

2019-05-31

[root@m1 ~]# kubectl get all -n ingress-nginx
NAME                                            READY   STATUS    RESTARTS   AGE
pod/default-http-backend-5c9bb94849-xx8d9       1/1     Running   1          178m
pod/nginx-ingress-controller-5bd8f6d78c-4vt82   0/1     Pending   0          103m

NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
service/default-http-backend   ClusterIP   10.101.248.28   <none>        80/TCP    3h33m

NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/default-http-backend       1/1     1            1           3h33m
deployment.apps/nginx-ingress-controller   0/1     1            0           3h33m

NAME                                                  DESIRED   CURRENT   READY   AGE
replicaset.apps/default-http-backend-5c9bb94849       1         1         1       3h33m
replicaset.apps/nginx-ingress-controller-5bd8f6d78c   1         1         0       140m
replicaset.apps/nginx-ingress-controller-65ccbbc7bb   0         0         0       3h33m
replicaset.apps/nginx-ingress-controller-fcc659f8f    0         0         0       147m

kubectl describe pod nginx-ingress-controller-5bd8f6d78c-4vt82 -n ingress-nginx

Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  29m (x61 over 104m)  default-scheduler  0/5 nodes are available: 5 node(s) didn't match node selector.
  Warning  FailedScheduling  20m (x11 over 23m)   default-scheduler  0/5 nodes are available: 5 node(s) didn't match node selector.
  Warning  FailedScheduling  56s (x18 over 20m)   default-scheduler  0/5 nodes are available: 5 node(s) didn't match node selector.

nginx-ingress-controller 启动不了一直Pending , 这是什么原因

写回答

1回答