Kube-system namespace

kube-system namespace

• Components: coredns, aws-node, kube-proxy, aws-load-balancer-controller

kubectl -n kube-system 
kubectl -n kube-system get pods

kubectl get sa -n kube-system
kubectl describe sa -n kube-system
kubectl get configmap -n kube-system

Helm install:

• helm install aws-cloudwatch-metrics --namespace kube-system eks/aws-cloudwatch-metrics
• helm install aws-load-balancer-controller

kubectl -n kube-system -l=k8s-app=kube-dns get pods
NAME                      READY   STATUS    RESTARTS   AGE
coredns-f47955f89-7ntw4   0/1     Pending   0          3h37m
coredns-f47955f89-sl79r   0/1     Pending   0          3h37m

kubectl -n kube-system -l=k8s-app=kube-dns get pods
NAME                      READY   STATUS    RESTARTS   AGE
coredns-f47955f89-d95dd   1/1     Running   0          45h
coredns-f47955f89-w746j   1/1     Running   0          45h

• kubectl get deployment metrics-server -n kube-system
• kubectl get secrets -n kube-system
• kubectl -n kube-system

EKS

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 describe -n kube-system configmap/aws-auth

Errors

• kube-system 43m Warning ClusterUnhealthy configmap/cluster-autoscaler-status
• Cluster has no ready nodes

Related

• kubectl get namespaces
• kubectl get daemonset
• kube-dns, kube-system Namespace
• coredns
• aws-node
• kube-public
• kube-node-lease
• kubectl edit service
• kubectl edit configmap

See also

• kube-system: kubectl get pods -n kube-system, kube-dns, aws-node
• Kubernetes namespaces: kubectl get namespaces, kube-system namespace, --namespace