1回答

月明星稀乌鹊南飞

提问者

2024-12-20

详细日志：

[root@master ~]# kubectl describe pod coredns-6d56c8448f-np2jk -n kube-system

Name:                 coredns-6d56c8448f-np2jk

Namespace:            kube-system

Priority:             2000000000

Priority Class Name:  system-cluster-critical

Node:                 <none>

Labels:               k8s-app=kube-dns

                      pod-template-hash=6d56c8448f

Annotations:          <none>

Status:               Pending

IP:                   

IPs:                  <none>

Controlled By:        ReplicaSet/coredns-6d56c8448f

Containers:

  coredns:

    Image:       registry.aliyuncs.com/google_containers/coredns:1.7.0

    Ports:       53/UDP, 53/TCP, 9153/TCP

    Host Ports:  0/UDP, 0/TCP, 0/TCP

    Args:

      -conf

      /etc/coredns/Corefile

    Limits:

      memory:  170Mi

    Requests:

      cpu:        100m

      memory:     70Mi

    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5

    Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=10s #success=1 #failure=3

    Environment:  <none>

    Mounts:

      /etc/coredns from config-volume (ro)

      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-zzk2c (ro)

Conditions:

  Type           Status

  PodScheduled   False 

Volumes:

  config-volume:

    Type:      ConfigMap (a volume populated by a ConfigMap)

    Name:      coredns

    Optional:  false

  coredns-token-zzk2c:

    Type:        Secret (a volume populated by a Secret)

    SecretName:  coredns-token-zzk2c

    Optional:    false

QoS Class:       Burstable

Node-Selectors:  kubernetes.io/os=linux

Tolerations:     CriticalAddonsOnly op=Exists

                 node-role.kubernetes.io/master:NoSchedule

                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s

                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s

Events:

  Type     Reason            Age                 From               Message

  ----     ------            ----                ----               -------

  Warning  FailedScheduling  44m                 default-scheduler  0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.

  Warning  FailedScheduling  46m (x34 over 51m)  default-scheduler  0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate.

0

1

清风

kubectl get nodes 看下结果

2024-12-23

共1条回复