Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ~$ kubectl describe po -n kube-system coredns-5644d7b6d9-dxkrn
- Name: coredns-5644d7b6d9-dxkrn
- Namespace: kube-system
- Priority: 2000000000
- Priority Class Name: system-cluster-critical
- Node: k8s-nsx-02/172.16.10.212
- Start Time: Sun, 26 Jan 2020 15:49:21 +0000
- Labels: k8s-app=kube-dns
- pod-template-hash=5644d7b6d9
- Annotations: <none>
- Status: Running
- IP: 172.16.1.3
- IPs:
- IP: 172.16.1.3
- Controlled By: ReplicaSet/coredns-5644d7b6d9
- Containers:
- coredns:
- Container ID: docker://534f1baaad5f9e7f82eefab76063770c10f0bc145455fa050ab9f8c498c89aef
- Image: k8s.gcr.io/coredns:1.6.2
- Image ID: docker-pullable://k8s.gcr.io/coredns@sha256:12eb885b8685b1b13a04ecf5c23bc809c2e57917252fd7b0be9e9c00644e8ee5
- Ports: 53/UDP, 53/TCP, 9153/TCP
- Host Ports: 0/UDP, 0/TCP, 0/TCP
- Args:
- -conf
- /etc/coredns/Corefile
- State: Waiting
- Reason: CrashLoopBackOff
- Last State: Terminated
- Reason: Completed
- Exit Code: 0
- Started: Sun, 26 Jan 2020 16:05:33 +0000
- Finished: Sun, 26 Jan 2020 16:07:23 +0000
- Ready: False
- Restart Count: 9
- 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-bz7j9 (ro)
- Conditions:
- Type Status
- Initialized True
- Ready False
- ContainersReady False
- PodScheduled True
- Volumes:
- config-volume:
- Type: ConfigMap (a volume populated by a ConfigMap)
- Name: coredns
- Optional: false
- coredns-token-bz7j9:
- Type: Secret (a volume populated by a Secret)
- SecretName: coredns-token-bz7j9
- Optional: false
- QoS Class: Burstable
- Node-Selectors: beta.kubernetes.io/os=linux
- Tolerations: CriticalAddonsOnly
- node-role.kubernetes.io/master:NoSchedule
- node.kubernetes.io/not-ready:NoExecute for 300s
- node.kubernetes.io/unreachable:NoExecute for 300s
- Events:
- Type Reason Age From Message
- ---- ------ ---- ---- -------
- Warning FailedScheduling 37m (x3 over 38m) default-scheduler 0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate.
- Warning FailedScheduling 22m (x13 over 36m) default-scheduler 0/2 nodes are available: 2 node(s) had taints that the pod didn't tolerate.
- Normal Scheduled 22m default-scheduler Successfully assigned kube-system/coredns-5644d7b6d9-dxkrn to k8s-nsx-02
- Normal Pulling 22m kubelet, k8s-nsx-02 Pulling image "k8s.gcr.io/coredns:1.6.2"
- Normal Pulled 22m kubelet, k8s-nsx-02 Successfully pulled image "k8s.gcr.io/coredns:1.6.2"
- Normal Created 22m (x4 over 22m) kubelet, k8s-nsx-02 Created container coredns
- Normal Pulled 22m (x3 over 22m) kubelet, k8s-nsx-02 Container image "k8s.gcr.io/coredns:1.6.2" already present on machine
- Normal Started 22m (x4 over 22m) kubelet, k8s-nsx-02 Started container coredns
- Normal Killing 22m (x4 over 22m) kubelet, k8s-nsx-02 Stopping container coredns
- Warning Unhealthy 22m (x2 over 22m) kubelet, k8s-nsx-02 Readiness probe failed: Get http://:8181/ready: dial tcp :8181: connect: connection refused
- Normal SandboxChanged 17m (x96 over 22m) kubelet, k8s-nsx-02 Pod sandbox changed, it will be killed and re-created.
- Warning Unhealthy 7m51s (x4 over 8m21s) kubelet, k8s-nsx-02 Readiness probe failed: Get http://172.16.1.3:8181/ready: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
- Warning BackOff 2m52s (x209 over 22m) kubelet, k8s-nsx-02 Back-off restarting failed container
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement