kubectl describe pods coredns-66bff467f8-9hq7j -n kube-system

노트에버 2020. 7. 1. 16:45

[root@master ~]# kubectl get pods --all-namespaces
NAMESPACE     NAME                                            READY   STATUS        RESTARTS   AGE
kube-system   coredns-66bff467f8-8f2r5                        1/1     Terminating   1          28d
kube-system   coredns-66bff467f8-9hq7j                        1/1     Running       0          84s
kube-system   coredns-66bff467f8-fsvdg                        1/1     Terminating   2          28d
kube-system   coredns-66bff467f8-tvrxz                        1/1     Running       0          84s
kube-system   etcd-localhost.localdomain                      1/1     Running       3          28d
kube-system   kube-apiserver-localhost.localdomain            1/1     Running       3          28d
kube-system   kube-controller-manager-localhost.localdomain   1/1     Running       2          28d
kube-system   kube-proxy-4qvbw                                1/1     Running       0          28d
kube-system   kube-proxy-9qx5s                                1/1     Running       3          28d
kube-system   kube-proxy-bb9k9                                1/1     Running       1          28d
kube-system   kube-scheduler-localhost.localdomain            1/1     Running       3          28d
kube-system   weave-net-chqps                                 2/2     Running       3          28d
kube-system   weave-net-dgc7c                                 2/2     Running       5          28d
kube-system   weave-net-dr9qw                                 2/2     Running       0          28d
[root@master ~]#  kubectl describe pods coredns-66bff467f8-9hq7j  -n kube-system

Name: coredns-66bff467f8-9hq7j

Namespace: kube-system

Priority: 2000000000

Priority Class Name: system-cluster-critical

Node: slave2/10.0.2.15

Start Time: Wed, 03 Jun 2020 16:13:42 +0900

Labels: k8s-app=kube-dns

pod-template-hash=66bff467f8

Annotations: <none>

Status: Running

IP: 10.32.0.2

IPs:

IP: 10.32.0.2

Controlled By: ReplicaSet/coredns-66bff467f8

Containers:

coredns:

Container ID: docker://28060dc555535b06b50dc0dcf8913d27aa7ac22a0bdc81725b71b3610a0a9114

Image: k8s.gcr.io/coredns:1.6.7

Image ID: docker-pullable://k8s.gcr.io/coredns@sha256:2c8d61c46f484d881db43b34d13ca47a269336e576c81cf007ca740fa9ec0800

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

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

Args:

-conf

/etc/coredns/Corefile

State: Running

Started: Wed, 03 Jun 2020 16:13:43 +0900

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 coredns-token-rbscr (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

coredns-token-rbscr:

Type: Secret (a volume populated by a Secret)

SecretName: coredns-token-rbscr

Optional: false

QoS Class: Burstable

Node-Selectors: 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

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

Normal Scheduled <unknown> default-scheduler Successfully assigned kube-system/coredns-66bff467f8-9hq7j to slave2

Normal Pulled 28d kubelet, slave2 Container image "k8s.gcr.io/coredns:1.6.7" already present on machine

Normal Created 28d kubelet, slave2 Created container coredns

Normal Started 28d kubelet, slave2 Started container coredns

저작자표시