Name: coredns-66bc5c9577-sd7lg Namespace: kube-system Priority: 2000000000 Priority Class Name: system-cluster-critical Service Account: coredns Node: controller/199.19.213.125 Start Time: Mon, 08 Jun 2026 09:25:44 +0000 Labels: k8s-app=kube-dns pod-template-hash=66bc5c9577 Annotations: Status: Running IP: 172.24.0.220 IPs: IP: 172.24.0.220 Controlled By: ReplicaSet/coredns-66bc5c9577 Containers: coredns: Container ID: containerd://3fc73d3eba7d393af221069b46da5d0c11bd2c939b3246aebe116b8be7418316 Image: registry.k8s.io/coredns/coredns:v1.12.1 Image ID: registry.k8s.io/coredns/coredns@sha256:e8c262566636e6bc340ece6473b0eed193cad045384401529721ddbe6463d31c Ports: 53/UDP (dns), 53/TCP (dns-tcp), 9153/TCP (metrics), 8080/TCP (liveness-probe), 8181/TCP (readiness-probe) Host Ports: 0/UDP (dns), 0/TCP (dns-tcp), 0/TCP (metrics), 0/TCP (liveness-probe), 0/TCP (readiness-probe) Args: -conf /etc/coredns/Corefile State: Running Started: Mon, 08 Jun 2026 09:27:52 +0000 Ready: True Restart Count: 0 Limits: memory: 170Mi Requests: cpu: 100m memory: 70Mi Liveness: http-get http://:liveness-probe/health delay=60s timeout=5s period=10s #success=1 #failure=5 Readiness: http-get http://:readiness-probe/ready delay=0s timeout=1s period=10s #success=1 #failure=3 Environment: Mounts: /etc/coredns from config-volume (ro) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9jclc (ro) Conditions: Type Status PodReadyToStartContainers True 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-9jclc: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt Optional: false DownwardAPI: true QoS Class: Burstable Node-Selectors: kubernetes.io/os=linux 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 5m6s default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. no new claims to deallocate, preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling. Normal Scheduled 4m10s default-scheduler Successfully assigned kube-system/coredns-66bc5c9577-sd7lg to controller Warning FailedCreatePodSandBox 3m20s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "2e7453b0378bbf80ed25dd0481ad8e37b797c32ddffffbb8a3285be25fef56ca": plugin type="cilium-cni" failed (add): unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get "http://localhost/v1/config": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory Is the agent running? Warning FailedCreatePodSandBox 2m16s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7e85262b3dc5319a0f858f73faabd84fd85866ac81dbd0a1b3af946354a27efc": plugin type="cilium-cni" failed (add): unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get "http://localhost/v1/config": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory Is the agent running? Normal Pulled 2m2s kubelet Container image "registry.k8s.io/coredns/coredns:v1.12.1" already present on machine Normal Created 2m2s kubelet Created container: coredns Normal Started 2m2s kubelet Started container coredns