Name:                 coredns-67659f764b-pg4sp
Namespace:            kube-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Service Account:      coredns
Node:                 instance/199.19.213.116
Start Time:           Wed, 06 May 2026 00:47:52 +0000
Labels:               k8s-app=kube-dns
                      pod-template-hash=67659f764b
Annotations:          <none>
Status:               Running
IP:                   10.0.0.246
IPs:
  IP:           10.0.0.246
Controlled By:  ReplicaSet/coredns-67659f764b
Containers:
  coredns:
    Container ID:  containerd://2ce307e9a22c28290d4448f087ee292beed5af1983419a22c27097bd53c25a6f
    Image:         harbor.atmosphere.dev/registry.k8s.io/coredns/coredns:v1.10.1
    Image ID:      harbor.atmosphere.dev/registry.k8s.io/coredns/coredns@sha256:a0ead06651cf580044aeb0a0feba63591858fb2e43ade8c9dea45a6a89ae7e5e
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Running
      Started:      Wed, 06 May 2026 00:47:53 +0000
    Ready:          True
    Restart Count:  0
    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 kube-api-access-bhfjx (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  kube-api-access-bhfjx:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              kubernetes.io/os=linux
                             openstack-control-plane=enabled
Tolerations:                 CriticalAddonsOnly op=Exists
                             node-role.kubernetes.io/control-plane: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  6m     default-scheduler  0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
  Normal   Scheduled         5m18s  default-scheduler  Successfully assigned kube-system/coredns-67659f764b-pg4sp to instance
  Normal   Pulled            5m17s  kubelet            Container image "harbor.atmosphere.dev/registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
  Normal   Created           5m17s  kubelet            Created container coredns
  Normal   Started           5m17s  kubelet            Started container coredns
  Warning  Unhealthy         5m17s  kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503