gistfile1.txt

_$ kp kube-system
NAME                                      READY   STATUS    RESTARTS   AGE
alb-ingress-controller-75c8c57884-5ch5k   1/1     Running   0          6m47s
coredns-59dfd6b59f-4kvm6                  0/1     Pending   0          10m
coredns-59dfd6b59f-8gn62                  0/1     Pending   0          11m
efs-csi-node-4frkb                        0/3     Pending   0          33m
efs-csi-node-5lztd                        0/3     Pending   0          33m
efs-csi-node-7d6j2                        0/3     Pending   0          33m
efs-csi-node-ll5cj                        0/3     Pending   0          5m48s
efs-csi-node-ssff6                        0/3     Pending   0          33m
efs-csi-node-vfcnp                        0/3     Pending   0          33m
paul.lupu@SVROLP00209:~/work/other/mi-kube-cluster/haproxy-ingress-elb:(master)\ 
 _$ kk get ns
NAME              STATUS   AGE
cert-manager      Active   34d
default           Active   37d
kube-node-lease   Active   37d
kube-public       Active   37d
kube-system       Active   37d
mi-dev            Active   35d
paul.lupu@SVROLP00209:~/work/other/mi-kube-cluster/haproxy-ingress-elb:(master)\ 
 _$ kk ^C
paul.lupu@SVROLP00209:~/work/other/mi-kube-cluster/haproxy-ingress-elb:(master)\ 
 _$ kk describe pod -n kube-system coredns-59dfd6b59f-4kvm6
Name:                 coredns-59dfd6b59f-4kvm6
Namespace:            kube-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Node:                 <none>
Labels:               eks.amazonaws.com/component=coredns
                      k8s-app=kube-dns
                      pod-template-hash=59dfd6b59f
Annotations:          eks.amazonaws.com/compute-type: ec2
                      kubernetes.io/psp: eks.privileged
Status:               Pending
IP:                   
IPs:                  <none>
Controlled By:        ReplicaSet/coredns-59dfd6b59f
Containers:
  coredns:
    Image:       602401143452.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.6.6
    Ports:       53/UDP, 53/TCP, 9153/TCP
    Host Ports:  0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    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://:8080/health delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /tmp from tmp (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-ljztw (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  tmp:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-ljztw:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-ljztw
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
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  8m13s               default-scheduler  0/5 nodes are available: 5 Insufficient pods.
  Warning  FailedScheduling  20s (x10 over 12m)  default-scheduler  0/6 nodes are available: 6 Insufficient pods.
paul.lupu@SVROLP00209:~/work/other/mi-kube-cluster/haproxy-ingress-elb:(master)\ 
 _$ kubectl describe deployment coredns --namespace kube-system
Name:                   coredns
Namespace:              kube-system
CreationTimestamp:      Sun, 12 Apr 2020 02:16:57 +0300
Labels:                 eks.amazonaws.com/component=coredns
                        k8s-app=kube-dns
                        kubernetes.io/name=CoreDNS
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               eks.amazonaws.com/component=coredns,k8s-app=kube-dns
Replicas:               2 desired | 2 updated | 2 total | 0 available | 2 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  1 max unavailable, 25% max surge
Pod Template:
  Labels:           eks.amazonaws.com/component=coredns
                    k8s-app=kube-dns
  Annotations:      eks.amazonaws.com/compute-type: ec2
  Service Account:  coredns
  Containers:
   coredns:
    Image:       602401143452.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.6.6
    Ports:       53/UDP, 53/TCP, 9153/TCP
    Host Ports:  0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    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://:8080/health delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /tmp from tmp (rw)
  Volumes:
   tmp:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
   config-volume:
    Type:               ConfigMap (a volume populated by a ConfigMap)
    Name:               coredns
    Optional:           false
  Priority Class Name:  system-cluster-critical
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Progressing    True    NewReplicaSetAvailable
  Available      False   MinimumReplicasUnavailable
OldReplicaSets:  <none>
NewReplicaSet:   coredns-59dfd6b59f (2/2 replicas created)
Events:          <none>