# Pastebin PkxoYpD9
[vagrant@localhost ~]$ kubectl describe po kube-dns-692378583-74ddf
Error from server (NotFound): pods "kube-dns-692378583-74ddf" not found
[vagrant@localhost ~]$ kubectl describe po kube-dns-692378583-74ddf -n kube-system
Name:		kube-dns-692378583-74ddf
Namespace:	kube-system
Node:		/
Labels:		k8s-app=kube-dns
		pod-template-hash=692378583
Annotations:	kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"kube-system","name":"kube-dns-692378583","uid":"e5fdb354-5b64-11e7-bc49-525400f31...
		scheduler.alpha.kubernetes.io/critical-pod=
Status:		Pending
IP:		
Controllers:	ReplicaSet/kube-dns-692378583
Containers:
  kubedns:
    Image:	gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.2
    Ports:	10053/UDP, 10053/TCP, 10055/TCP
    Args:
      --domain=cluster.local.
      --dns-port=10053
      --config-dir=/kube-dns-config
      --v=2
    Limits:
      memory:	170Mi
    Requests:
      cpu:	100m
      memory:	70Mi
    Liveness:	http-get http://:10054/healthcheck/kubedns delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:	http-get http://:8081/readiness delay=3s timeout=5s period=10s #success=1 #failure=3
    Environment:
      PROMETHEUS_PORT:	10055
    Mounts:
      /kube-dns-config from kube-dns-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-9cgsv (ro)
  dnsmasq:
    Image:	gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.2
    Ports:	53/UDP, 53/TCP
    Args:
      -v=2
      -logtostderr
      -configDir=/etc/k8s/dns/dnsmasq-nanny
      -restartDnsmasq=true
      --
      -k
      --cache-size=1000
      --log-facility=-
      --server=/cluster.local/127.0.0.1#10053
      --server=/in-addr.arpa/127.0.0.1#10053
      --server=/ip6.arpa/127.0.0.1#10053
    Requests:
      cpu:		150m
      memory:		20Mi
    Liveness:		http-get http://:10054/healthcheck/dnsmasq delay=60s timeout=5s period=10s #success=1 #failure=5
    Environment:	<none>
    Mounts:
      /etc/k8s/dns/dnsmasq-nanny from kube-dns-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-9cgsv (ro)
  sidecar:
    Image:	gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.2
    Port:	10054/TCP
    Args:
      --v=2
      --logtostderr
      --probe=kubedns,127.0.0.1:10053,kubernetes.default.svc.cluster.local,5,A
      --probe=dnsmasq,127.0.0.1:53,kubernetes.default.svc.cluster.local,5,A
    Requests:
      cpu:		10m
      memory:		20Mi
    Liveness:		http-get http://:10054/metrics delay=60s timeout=5s period=10s #success=1 #failure=5
    Environment:	<none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-9cgsv (ro)
Conditions:
  Type		Status
  PodScheduled 	False 
Volumes:
  kube-dns-config:
    Type:	ConfigMap (a volume populated by a ConfigMap)
    Name:	kube-dns
    Optional:	true
  kube-dns-token-9cgsv:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	kube-dns-token-9cgsv
    Optional:	false
QoS Class:	Burstable
Node-Selectors:	<none>
Tolerations:	CriticalAddonsOnly=:Exists
		node-role.kubernetes.io/master=:NoSchedule
		node.alpha.kubernetes.io/notReady=:Exists:NoExecute for 300s
		node.alpha.kubernetes.io/unreachable=:Exists:NoExecute for 300s
Events:
  FirstSeen	LastSeen	Count	From			SubObjectPath	Type		Reason			Message
  ---------	--------	-----	----			-------------	--------	------			-------
  19m		18m		8	default-scheduler			Warning		FailedScheduling	no nodes available to schedule pods
  17m		21s		63	default-scheduler			Warning		FailedScheduling	No nodes are available that match all of the following predicates:: Insufficient cpu (1).