This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-14 13:42
Elapsed18m54s
Revisionmaster

Test Failures


kubetest2 Up 15m46s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 159 lines ...
I0714 13:43:28.487760    5937 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0714 13:43:28.489912    5937 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-70-g32d293b0ff/linux/amd64/kops
I0714 13:43:29.792742    5937 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519
I0714 13:43:29.805735    5937 up.go:44] Cleaning up any leaked resources from previous cluster
I0714 13:43:29.805865    5937 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0714 13:43:29.805884    5937 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
W0714 13:43:30.304084    5937 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0714 13:43:30.304136    5937 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops delete cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --yes
I0714 13:43:30.304149    5937 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops delete cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --yes
I0714 13:43:30.326058    5969 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io" not found
I0714 13:43:30.794401    5937 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/14 13:43:30 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
I0714 13:43:30.803660    5937 http.go:37] curl https://ip.jsb.workers.dev
I0714 13:43:30.950699    5937 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops create cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.5.0_HVM-20211103-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.224.48.110/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0714 13:43:30.950738    5937 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops create cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.5.0_HVM-20211103-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.224.48.110/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0714 13:43:30.971777    5979 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0714 13:43:30.999083    5979 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0714 13:43:31.474419    5979 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 529 lines ...

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
W0714 13:44:11.550177    6018 validate_cluster.go:232] (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
W0714 13:44:21.590587    6018 validate_cluster.go:232] (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
W0714 13:44:31.626908    6018 validate_cluster.go:232] (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
W0714 13:44:41.667870    6018 validate_cluster.go:232] (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
W0714 13:44:51.706732    6018 validate_cluster.go:232] (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
W0714 13:45:01.746674    6018 validate_cluster.go:232] (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
W0714 13:45:11.793243    6018 validate_cluster.go:232] (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
W0714 13:45:21.838227    6018 validate_cluster.go:232] (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
W0714 13:45:31.891216    6018 validate_cluster.go:232] (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
W0714 13:45:41.932902    6018 validate_cluster.go:232] (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
W0714 13:45:51.970590    6018 validate_cluster.go:232] (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
W0714 13:46:02.007962    6018 validate_cluster.go:232] (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
W0714 13:46:12.052101    6018 validate_cluster.go:232] (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
W0714 13:46:22.090645    6018 validate_cluster.go:232] (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
W0714 13:46:32.129212    6018 validate_cluster.go:232] (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
W0714 13:46:42.163050    6018 validate_cluster.go:232] (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
W0714 13:46:52.197068    6018 validate_cluster.go:232] (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
W0714 13:47:02.234575    6018 validate_cluster.go:232] (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
W0714 13:47:12.267840    6018 validate_cluster.go:232] (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
W0714 13:47:22.315211    6018 validate_cluster.go:232] (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
W0714 13:47:32.360171    6018 validate_cluster.go:232] (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
W0714 13:47:42.399645    6018 validate_cluster.go:232] (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
W0714 13:47:52.434082    6018 validate_cluster.go:232] (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
W0714 13:48:02.482447    6018 validate_cluster.go:232] (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
W0714 13:48:12.517190    6018 validate_cluster.go:232] (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
W0714 13:48:22.557216    6018 validate_cluster.go:232] (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
W0714 13:48:32.595112    6018 validate_cluster.go:232] (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
W0714 13:48:42.629538    6018 validate_cluster.go:232] (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
W0714 13:48:52.668990    6018 validate_cluster.go:232] (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
W0714 13:49:02.702130    6018 validate_cluster.go:232] (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
W0714 13:49:12.741047    6018 validate_cluster.go:232] (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
W0714 13:49:22.790939    6018 validate_cluster.go:232] (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 7 lines ...
Machine	i-0204c1f13ab0ab245				machine "i-0204c1f13ab0ab245" has not yet joined cluster
Machine	i-0bb90e9474e8b7e85				machine "i-0bb90e9474e8b7e85" has not yet joined cluster
Machine	i-0cf86184e6a396bba				machine "i-0cf86184e6a396bba" has not yet joined cluster
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:49:34.085830    6018 validate_cluster.go:232] (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 9 lines ...
Machine	i-0204c1f13ab0ab245				machine "i-0204c1f13ab0ab245" has not yet joined cluster
Node	ip-172-20-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:49:45.014684    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:49:55.906913    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:50:06.875099    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:50:17.756323    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:50:28.724521    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:50:40.755035    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:50:51.664019    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:51:02.595439    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:51:13.577880    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:51:24.501462    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:51:35.490773    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:51:46.640170    6018 validate_cluster.go:232] (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-34-133.us-east-2.compute.internal	node "ip-172-20-34-133.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready

Validation Failed
W0714 13:51:57.637053    6018 validate_cluster.go:232] (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-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/ebs-csi-controller-7f79b4694f-2hjn2	system-cluster-critical pod "ebs-csi-controller-7f79b4694f-2hjn2" is pending

Validation Failed
W0714 13:52:08.638639    6018 validate_cluster.go:232] (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-37-182.us-east-2.compute.internal	node "ip-172-20-37-182.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-43-177.us-east-2.compute.internal	node "ip-172-20-43-177.us-east-2.compute.internal" of role "master" is not ready
Node	ip-172-20-56-183.us-east-2.compute.internal	node "ip-172-20-56-183.us-east-2.compute.internal" of role "node" is not ready
Node	ip-172-20-59-157.us-east-2.compute.internal	node "ip-172-20-59-157.us-east-2.compute.internal" of role "node" is not ready
Pod	kube-system/ebs-csi-controller-7f79b4694f-2hjn2	system-cluster-critical pod "ebs-csi-controller-7f79b4694f-2hjn2" is pending

Validation Failed
W0714 13:52:19.638576    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:52:30.667765    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:52:41.646660    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:52:52.541586    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:53:03.449805    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:53:14.471491    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:53:25.545902    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:53:36.533339    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:53:47.533029    6018 validate_cluster.go:232] (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 16 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:53:58.402816    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:54:09.407509    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:54:20.285172    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:54:31.235238    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:54:42.182362    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:54:53.127946    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:55:04.155782    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:55:15.121106    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:55:26.026990    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:55:37.037881    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:55:48.026349    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:55:59.001716    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:56:09.923666    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:56:20.885360    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:56:31.775236    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:56:42.846434    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:56:53.726102    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:57:04.655437    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:57:15.756732    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:57:26.642677    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:57:37.621458    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:57:48.498507    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:57:59.501677    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:58:10.413350    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:58:21.364259    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:58:32.324715    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:58:43.225983    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:58:54.098083    6018 validate_cluster.go:232] (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 18 lines ...
Pod	kube-system/ebs-csi-node-5kghr			system-node-critical pod "ebs-csi-node-5kghr" is pending
Pod	kube-system/ebs-csi-node-5nmm6			system-node-critical pod "ebs-csi-node-5nmm6" is pending
Pod	kube-system/ebs-csi-node-flhft			system-node-critical pod "ebs-csi-node-flhft" is pending
Pod	kube-system/ebs-csi-node-x5vvs			system-node-critical pod "ebs-csi-node-x5vvs" is pending
Pod	kube-system/ebs-csi-node-zkmdp			system-node-critical pod "ebs-csi-node-zkmdp" is pending

Validation Failed
W0714 13:59:05.041139    6018 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0714 13:59:15.049936    5937 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0714 13:59:15.049990    5937 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0714 13:59:35.520547    5937 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops get cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
I0714 13:59:35.520589    5937 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops get cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
I0714 13:59:36.067201    5937 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops get instancegroups --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
I0714 13:59:36.067242    5937 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/b609f135-037a-11ed-a16d-969e568a80d4/kops get instancegroups --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
... skipping 263 lines ...
route-table:rtb-06e1044b4b8bcbf43	ok
vpc:vpc-0f26c4ddbd4293245	ok
dhcp-options:dopt-0c3c75ae6a011ac8e	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace