Difference between revisions of "Kubectl get pods -n kube-system"
Jump to navigation
Jump to search
(3 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
[[kubectl get pods]] -n [[kube-system]] | [[kubectl get pods]] -n [[kube-system]] | ||
− | * [[aws-node]], [[coredns]], [[kube-proxy]], [[aws-load-balancer-controller]], [[snapshot-controller]], [[ssm-installer]], [[ebs-csi-controller]], [[ebs-csi-node]] | + | * <code>[[aws-node]], [[coredns]], [[kube-proxy]], [[metrics-server]], [[aws-load-balancer-controller]], [[snapshot-controller]], [[ssm-installer]], [[ebs-csi-controller]], [[ebs-csi-node]], [[efs-csi-node]], [[efs-csi-controller]]</code> |
== [[EKS]]: [[EKS addons]] == | == [[EKS]]: [[EKS addons]] == |
Latest revision as of 12:22, 22 February 2024
kubectl get pods -n kube-system
aws-node, coredns, kube-proxy, metrics-server, aws-load-balancer-controller, snapshot-controller, ssm-installer, ebs-csi-controller, ebs-csi-node, efs-csi-node, efs-csi-controller
EKS: EKS addons[edit]
kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE aws-node-4zx4r 1/1 Running 0 4d18h aws-node-hsxyz 1/1 Running 0 4d18h aws-node-w59pg 1/1 Running 0 4d18h coredns-5c778788f4-2xyz 0/1 Pending 0 41h coredns-5c778788f4-dyzk 0/1 Pending 0 41h kube-proxy-m5912 1/1 Running 0 4d18h kube-proxy-vbx32 1/1 Running 0 4d18h kube-proxy-w9v45 1/1 Running 0 4d18h
After installing aws-load-balancer-controller
kubectl -n kube-system get pods NAME READY STATUS RESTARTS AGE aws-load-balancer-controller-5bcbf46bdb-b4znr 1/1 Running 0 2m46s aws-load-balancer-controller-5bcbf46bdb-xgs4s 1/1 Running 0 2m46s aws-node-4zqph 1/1 Running 0 4d23h aws-node-hsxn8 1/1 Running 0 4d23h aws-node-w59pg 1/1 Running 0 4d23h coredns-5c778788f4-2x4vq 1/1 Running 0 45h coredns-5c778788f4-dlhx5 1/1 Running 0 45h kube-proxy-m59nt 1/1 Running 0 4d23h kube-proxy-vbx9q 1/1 Running 0 4d23h kube-proxy-w9vms 1/1 Running 0 4d23h
kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE aws-node-xkvqs 2/2 Running 0 25d coredns-6dc8c57fb9-sppjf 1/1 Running 0 25d coredns-6dc8c57fb9-x2hjw 1/1 Running 0 25d ebs-csi-controller-6d679944f5-h99sx 6/6 Running 0 25d ebs-csi-controller-6d679944f5-mbxbd 6/6 Running 0 25d ebs-csi-node-7rzfb 3/3 Running 0 25d kube-proxy-5p7zf 1/1 Running 0 25d snapshot-controller-5c644cf9f9-k27sq 1/1 Running 0 25d snapshot-controller-5c644cf9f9-p9nlx 1/1 Running 0 25d ssm-installer-rcvpx 1/1 Running 621 (55m ago) 25d
kubectl get pods -n kube-system NAME READY STATUS RESTARTS AGE aws-node-7wqrv 2/2 Running 0 72d aws-node-rfld6 2/2 Running 0 26h aws-node-w75dq 0/2 Init:0/1 0 26h coredns-7847877569-4bwsg 1/1 Running 0 26h coredns-7847877569-8d8sd 1/1 Running 0 26h coredns-7847877569-t9jrm 0/1 ContainerCreating 0 26h ebs-csi-controller-74d5f9989c-nl9f9 6/6 Running 2 (33d ago) 72d ebs-csi-controller-74d5f9989c-sfvl4 6/6 Running 2 (33d ago) 72d ebs-csi-node-c5pcs 3/3 Running 0 72d ebs-csi-node-mt9lg 2/3 CreateContainerError 209 72d ebs-csi-node-p2vwk 3/3 Running 0 72d efs-csi-controller-5cb959b59-fvs64 3/3 Running 0 81m efs-csi-controller-5cb959b59-xh5qv 3/3 Running 0 81m efs-csi-node-66mxl 0/3 Terminating 0 26h efs-csi-node-b4hfp 3/3 Running 0 81m efs-csi-node-jjwpl 3/3 Running 0 72d kube-proxy-jpdlq 1/1 Running 0 26h kube-proxy-lwtsd 1/1 Running 0 26h kube-proxy-tgczm 0/1 ContainerCreating 0 26h metrics-server-57766c474b-nxszl 1/1 Running 0 72d snapshot-controller-5c644cf9f9-j6ps4 1/1 Running 0 72d snapshot-controller-5c644cf9f9-s8w45 1/1 Running 0 72d ssm-installer-w298b 1/1 Running 1741 (33m ago) 72d ssm-installer-wqpnf 1/1 Running 1741 (33m ago) 72d ssm-installer-z52nx 0/1 CreateContainerError 1738 72d
Related[edit]
See also[edit]
Advertising: