❯ kubectl.aws describe pod test-ingress -n kube-system                                                                                                                                       [09:12:58]
Name:         test-ingress
Namespace:    kube-system
Node:         ip-10-46-201-159.aws.lmig.com/10.46.200.139
Start Time:   Wed, 04 Apr 2018 08:45:42 -0400
Labels:       purpose=test-ingress
Annotations:  kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"Pod","metadata":{"annotations":{},"labels":{"purpose":"test-ingress"},"name":"test-ingress","namespace":"kube-system"},"spec...
Status:       Succeeded
IP:           10.46.203.98
Containers:
 test-ingress:
   Container ID:  docker://4cd419d73e6e265c1ad8eabd54bc5c5e5b8120a4b193531254fe9436020d4444
   Image:         michaell71/alb-ingress-controller:1.0-alpha.3
   Image ID:      docker-pullable://michaell71/alb-ingress-controller@sha256:ef261205dc5d271f199248395eeea2045a557a8b4bc84ebd4fcbac96e1c55fab
   Port:          <none>
   Command:
     sleep
   Args:
     600
   State:          Terminated
     Reason:       Completed
     Exit Code:    0
     Started:      Wed, 04 Apr 2018 08:45:43 -0400
     Finished:     Wed, 04 Apr 2018 08:55:43 -0400
   Ready:          False
   Restart Count:  0
   Environment:    <none>
   Mounts:
     /var/run/secrets/kubernetes.io/serviceaccount from saingress-token-pkb7m (ro)
Conditions:
 Type           Status
 Initialized    True
 Ready          False
 PodScheduled   True
Volumes:
 saingress-token-pkb7m:
   Type:        Secret (a volume populated by a Secret)
   SecretName:  saingress-token-pkb7m
   Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     <none>
Events:
 Type     Reason                 Age   From                                    Message
 ----     ------                 ----  ----                                    -------
 Normal   Scheduled              27m   default-scheduler                       Successfully assigned test-ingress to ip-10-46-201-159.aws.lmig.com
 Warning  FailedScheduling       27m   default-scheduler                       Binding rejected: Operation cannot be fulfilled on pods/binding "test-ingress": pod test-ingress is already assigned to node "ip-10-46-201-159.aws.lmig.com"
 Normal   SuccessfulMountVolume  27m   kubelet, ip-10-46-201-159.aws.lmig.com  MountVolume.SetUp succeeded for volume "saingress-token-pkb7m"
 Normal   Pulled                 27m   kubelet, ip-10-46-201-159.aws.lmig.com  Container image "michaell71/alb-ingress-controller:1.0-alpha.3" already present on machine
 Normal   Created                27m   kubelet, ip-10-46-201-159.aws.lmig.com  Created container
 Normal   Started                27m   kubelet, ip-10-46-201-159.aws.lmig.com  Started container