Difference between revisions of "Kubectl get pods -n kube-system"
Jump to navigation
Jump to search
| 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]] | + | * [[aws-node]], [[coredns]], [[kube-proxy]], [[aws-load-balancer-controller]], [[snapshot-controller]] |
== [[EKS]]: [[EKS addons]] == | == [[EKS]]: [[EKS addons]] == | ||
Revision as of 12:18, 22 February 2024
kubectl get pods -n kube-system
EKS: EKS addons
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
Related
See also
Advertising:
