This job view page is being replaced by Spyglass soon. Check out the new job view.
PRolemarkus: Enable IRSA for CCM
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-24 10:35
Elapsed26m12s
Revision362ace21dbeae54d65bdc561573e0a44b40621c0
Refs 11818

No Test Failures!


Error lines from build-log.txt

... skipping 623 lines ...
  zone: eu-west-3a
vpc:
  id: vpc-0ca564a088d9d1388
I0624 10:39:54.307794    4229 dumplogs.go:70] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops get cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io -o yaml
I0624 10:39:54.830630    4229 dumplogs.go:70] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops get instancegroups --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io -o yaml
I0624 10:39:55.647198    4229 dumplogs.go:89] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info
W0624 10:39:55.721762    4229 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0624 10:39:55.721839    4229 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --yes
I0624 10:39:55.739895   11794 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 10:39:55.739999   11794 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
W0624 10:39:57.362365   11794 aws_cloud.go:707] Skipping ASG arn:aws:autoscaling:eu-west-3:768319786644:autoScalingGroup:16126a86-4068-4aec-8d08-c418b3a52983:autoScalingGroupName/master-eu-west-3a.masters.e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io (which matches tags): Delete in progress
W0624 10:39:57.362418   11794 aws_cloud.go:707] Skipping ASG arn:aws:autoscaling:eu-west-3:768319786644:autoScalingGroup:df05c739-cf40-407a-9a66-ba98254fbb88:autoScalingGroupName/nodes-eu-west-3a.e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io (which matches tags): Delete in progress
TYPE			NAME									ID
... skipping 214 lines ...
route-table:rtb-0951b53241d6c3959	ok
vpc:vpc-0ca564a088d9d1388	ok
dhcp-options:dopt-0774fe65e6b54a4ee	ok

Deleted cluster: "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io"
I0624 10:41:57.967767    4229 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/24 10:41:57 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0624 10:41:57.981064    4229 http.go:37] curl https://ip.jsb.workers.dev
I0624 10:41:58.118229    4229 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.0-beta.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210621 --channel=alpha --networking=kubenet --container-runtime=containerd --override=cluster.spec.cloudControllerManager.cloudProvider=aws --admin-access 35.202.129.61/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0624 10:41:58.138308   11805 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 10:41:58.139046   11805 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0624 10:41:58.195667   11805 create_cluster.go:739] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0624 10:41:58.676503   11805 new_cluster.go:1054]  Cloud Provider ID = aws
... skipping 31 lines ...

I0624 10:42:22.120547    4229 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0624 10:42:22.140347   11826 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 10:42:22.140635   11826 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

W0624 10:42:23.142603   11826 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:42:33.179191   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:42:43.217977   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:42:53.265294   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:43:03.297072   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:43:13.336938   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:43:23.372355   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:43:33.419874   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:43:43.451382   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:43:53.488777   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:44:05.230506   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:44:15.432423   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:44:25.481762   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:44:35.528800   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:44:45.564212   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:44:55.594997   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:45:05.628548   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:45:15.663647   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:45:25.714080   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0624 10:45:35.762159   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 8 lines ...
Machine	i-0c27c9c5fd2b98285				machine "i-0c27c9c5fd2b98285" has not yet joined cluster
Machine	i-0e69a7b3449c61d2e				machine "i-0e69a7b3449c61d2e" has not yet joined cluster
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-slfr7	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-slfr7" is pending
Pod	kube-system/coredns-f45c4bf76-h48pn		system-cluster-critical pod "coredns-f45c4bf76-h48pn" is pending

Validation Failed
W0624 10:45:47.099733   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 10 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-slfr7	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-slfr7" is pending
Pod	kube-system/coredns-f45c4bf76-h48pn		system-cluster-critical pod "coredns-f45c4bf76-h48pn" is pending
Pod	kube-system/ebs-csi-node-jldkg			system-node-critical pod "ebs-csi-node-jldkg" is pending

Validation Failed
W0624 10:45:58.147661   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 13 lines ...
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-slfr7	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-slfr7" is pending
Pod	kube-system/coredns-f45c4bf76-h48pn		system-cluster-critical pod "coredns-f45c4bf76-h48pn" is pending
Pod	kube-system/ebs-csi-node-ddvs9			system-node-critical pod "ebs-csi-node-ddvs9" is pending
Pod	kube-system/ebs-csi-node-xpjnv			system-node-critical pod "ebs-csi-node-xpjnv" is pending

Validation Failed
W0624 10:46:09.132356   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 13 lines ...
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-slfr7	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-slfr7" is pending
Pod	kube-system/coredns-f45c4bf76-h48pn		system-cluster-critical pod "coredns-f45c4bf76-h48pn" is pending
Pod	kube-system/ebs-csi-node-hjdrn			system-node-critical pod "ebs-csi-node-hjdrn" is pending

Validation Failed
W0624 10:46:20.082526   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 12 lines ...
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending
Pod	kube-system/ebs-csi-node-hjdrn			system-node-critical pod "ebs-csi-node-hjdrn" is pending

Validation Failed
W0624 10:46:31.016596   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:46:42.036630   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:46:53.007541   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:47:04.005354   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 12 lines ...
Node	ip-172-20-53-57.us-east-2.compute.internal				node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal				node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal				node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp					system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-66.us-east-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-66.us-east-2.compute.internal" is pending

Validation Failed
W0624 10:47:14.964028   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:47:25.881167   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:47:36.839385   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:47:47.885783   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:47:58.788753   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:48:09.755634   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:48:20.596425   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:48:31.591467   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:48:43.578612   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:48:54.547743   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:49:05.505702   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:49:16.533190   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:49:27.598153   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:49:38.670330   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:49:49.636631   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:50:00.619446   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:50:11.655473   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:50:22.667343   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:50:33.676899   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:50:44.679646   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:50:55.873736   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:51:06.976899   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:51:17.962297   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:51:28.947537   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:51:39.924345   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:51:50.954578   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:52:02.007662   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:52:13.010378   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:52:24.019175   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:52:35.040075   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:52:46.033814   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:52:57.085234   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:53:08.042745   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:53:19.011365   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:53:30.116310   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:53:41.017092   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:53:52.174378   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:54:03.273510   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:54:14.346455   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:54:25.299176   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:54:36.238450   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:54:47.197102   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:54:58.165017   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:55:09.072783   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:55:20.022404   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:55:31.025384   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:55:41.946453   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:55:52.913085   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:56:03.889787   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:56:14.890596   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:56:25.842881   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:56:36.876877   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:56:47.854213   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:56:58.823962   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:57:09.915839   11826 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

... skipping 11 lines ...
Node	ip-172-20-51-38.us-east-2.compute.internal	node "ip-172-20-51-38.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-53-57.us-east-2.compute.internal	node "ip-172-20-53-57.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-56-145.us-east-2.compute.internal	node "ip-172-20-56-145.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-187.us-east-2.compute.internal	node "ip-172-20-59-187.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-69gwp		system-cluster-critical pod "coredns-f45c4bf76-69gwp" is pending

Validation Failed
W0624 10:57:20.966729   11826 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0624 10:57:30.971258    4229 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0624 10:57:30.988049   11837 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 10:57:30.988151   11837 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/06/24 10:57:37 Dumping node ip-172-20-46-66.us-east-2.compute.internal
2021/06/24 10:57:38 Dumping node ip-172-20-51-38.us-east-2.compute.internal
2021/06/24 10:57:41 Dumping node ip-172-20-53-57.us-east-2.compute.internal
... skipping 1446 lines ...
route-table:rtb-0695e59ef117fc1f1	ok
vpc:vpc-0de0581ddb13bd006	ok
dhcp-options:dopt-03b010559578ffeda	ok
Deleted kubectl config for e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

Deleted cluster: "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...