This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-09 15:36
Elapsed19m41s
Revisionmaster

Test Failures


kubetest2 Up 15m44s

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 ...
I0709 15:37:55.350073    5972 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0709 15:37:55.353634    5972 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-61-g85c172ba32/linux/amd64/kops
I0709 15:37:56.224236    5972 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519
I0709 15:37:56.238601    5972 up.go:44] Cleaning up any leaked resources from previous cluster
I0709 15:37:56.238839    5972 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0709 15:37:56.238884    5972 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0709 15:37:56.826617    5972 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0709 15:37:56.826715    5972 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops delete cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --yes
I0709 15:37:56.826734    5972 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops delete cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --yes
I0709 15:37:56.860740    6006 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io" not found
I0709 15:37:57.401849    5972 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/09 15:37: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
I0709 15:37:57.413316    5972 http.go:37] curl https://ip.jsb.workers.dev
I0709 15:37:57.524932    5972 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops create cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.11 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220706 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.232.18.61/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0709 15:37:57.525037    5972 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops create cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.11 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220706 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.232.18.61/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0709 15:37:57.565786    6016 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0709 15:37:57.606638    6016 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0709 15:37:58.127689    6016 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
W0709 15:38:37.841406    6056 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
W0709 15:38:47.895160    6056 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
W0709 15:38:57.944898    6056 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
W0709 15:39:07.983838    6056 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
W0709 15:39:18.027228    6056 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
W0709 15:39:28.073715    6056 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
W0709 15:39:38.119240    6056 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
W0709 15:39:48.161511    6056 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
W0709 15:39:58.206878    6056 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
W0709 15:40:08.243034    6056 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
W0709 15:40:18.280465    6056 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
W0709 15:40:28.320280    6056 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
W0709 15:40:38.359349    6056 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
W0709 15:40:48.396297    6056 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
W0709 15:40:58.434422    6056 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
W0709 15:41:08.473600    6056 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
W0709 15:41:18.529052    6056 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
W0709 15:41:28.580870    6056 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
W0709 15:41:38.634611    6056 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
W0709 15:41:48.675104    6056 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
W0709 15:41:58.714806    6056 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
W0709 15:42:08.747774    6056 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
W0709 15:42:18.796194    6056 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
W0709 15:42:28.839825    6056 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
W0709 15:42:38.882398    6056 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
W0709 15:42:48.923517    6056 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
W0709 15:42:58.981192    6056 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
W0709 15:43:09.027139    6056 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
W0709 15:43:19.068035    6056 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
W0709 15:43:29.110025    6056 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
W0709 15:43:39.145141    6056 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
W0709 15:43:49.202544    6056 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
W0709 15:43:59.258202    6056 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
W0709 15:44:09.304729    6056 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
W0709 15:44:19.345116    6056 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-controller-dbfd64777-5bj7c	system-cluster-critical pod "ebs-csi-controller-dbfd64777-5bj7c" is pending
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:44:30.672391    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:44:41.581162    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:44:52.642892    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:45:03.602255    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:45:14.584043    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:45:25.650881    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:45:36.524996    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:45:47.536091    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:45:58.468313    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:46:09.373277    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:46:20.327392    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:46:31.283424    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:46:42.260537    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:46:53.237164    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:47:04.323130    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:47:15.252666    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:47:26.190274    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:47:37.244818    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:47:48.250900    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:47:59.171747    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:48:10.026987    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:48:21.122064    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:48:32.142189    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:48:43.156669    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:48:54.190686    6056 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 19 lines ...
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:49:05.206846    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:49:16.189434    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:49:28.300866    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:49:39.425472    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:49:50.458498    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:50:01.499402    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:50:12.421545    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:50:23.549019    6056 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-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:50:34.599677    6056 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 23 lines ...
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:50:45.556455    6056 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 21 lines ...
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:50:56.509072    6056 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 17 lines ...
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:51:07.430630    6056 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 13 lines ...
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-w6mfz			system-node-critical pod "ebs-csi-node-w6mfz" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:51:18.399501    6056 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 ...
Pod	kube-system/ebs-csi-controller-dbfd64777-5bj7c	system-cluster-critical pod "ebs-csi-controller-dbfd64777-5bj7c" is pending
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-xw5h7			system-node-critical pod "ebs-csi-node-xw5h7" is pending
Pod	kube-system/ebs-csi-node-z2fb8			system-node-critical pod "ebs-csi-node-z2fb8" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:51:29.373733    6056 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 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/ebs-csi-controller-dbfd64777-5bj7c	system-cluster-critical pod "ebs-csi-controller-dbfd64777-5bj7c" is pending
Pod	kube-system/ebs-csi-node-g9pvd			system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-z9fvp			system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:51:40.254762    6056 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 ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-g9pvd	system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-z9fvp	system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:51:51.174827    6056 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 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5fcc7b6498-lns5c	system-cluster-critical pod "coredns-5fcc7b6498-lns5c" is not ready (coredns)
Pod	kube-system/ebs-csi-node-g9pvd		system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-z9fvp		system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:52:02.192326    6056 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 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5fcc7b6498-8dmkb	system-cluster-critical pod "coredns-5fcc7b6498-8dmkb" is not ready (coredns)
Pod	kube-system/ebs-csi-node-g9pvd		system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-z9fvp		system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:52:13.301906    6056 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 ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-g9pvd	system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-z9fvp	system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:52:24.190157    6056 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 ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-g9pvd	system-node-critical pod "ebs-csi-node-g9pvd" is pending
Pod	kube-system/ebs-csi-node-z9fvp	system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:52:35.106207    6056 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 6 lines ...
ip-172-20-54-119.us-east-2.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/ebs-csi-node-z9fvp	system-node-critical pod "ebs-csi-node-z9fvp" is pending

Validation Failed
W0709 15:52:46.024060    6056 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 49 lines ...
ip-172-20-41-120.us-east-2.compute.internal	node	True
ip-172-20-49-206.us-east-2.compute.internal	node	True
ip-172-20-54-119.us-east-2.compute.internal	master	True

Your cluster e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io is ready
I0709 15:53:29.801140    6056 validate_cluster.go:220] (will retry): cluster passed validation 4 consecutive times
Error: Validation failed: wait time exceeded during validation
I0709 15:53:39.816701    5972 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0709 15:53:39.816880    5972 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0709 15:54:02.336496    5972 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops get cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
I0709 15:54:02.336560    5972 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops get cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
I0709 15:54:02.889447    5972 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops get instancegroups --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
I0709 15:54:02.889500    5972 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/d2996ccd-ff9c-11ec-9fb7-3e7cb3b25c5e/kops get instancegroups --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
... skipping 345 lines ...
route-table:rtb-08f5c72800d6025df	ok
vpc:vpc-0651bdffd190c911c	ok
dhcp-options:dopt-07e809008f5230c72	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io

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