This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-23 02:16
Elapsed18m9s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 132 lines ...
I0923 02:17:33.913978    4669 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0923 02:17:33.916111    4669 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.2+v1.22.0-beta.1-101-g894ecb0af1/linux/amd64/kops
I0923 02:17:34.613779    4669 up.go:43] Cleaning up any leaked resources from previous cluster
I0923 02:17:34.613998    4669 dumplogs.go:40] /logs/artifacts/365c0273-1c14-11ec-883b-c61df66c07e7/kops toolbox dump --name e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0923 02:17:34.634518    4691 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 02:17:34.634635    4691 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io" not found
W0923 02:17:35.145866    4669 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0923 02:17:35.145936    4669 down.go:48] /logs/artifacts/365c0273-1c14-11ec-883b-c61df66c07e7/kops delete cluster --name e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io --yes
I0923 02:17:35.166305    4700 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 02:17:35.167108    4700 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io" not found
I0923 02:17:35.662787    4669 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/23 02:17:35 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
I0923 02:17:35.671094    4669 http.go:37] curl https://ip.jsb.workers.dev
I0923 02:17:35.768813    4669 up.go:144] /logs/artifacts/365c0273-1c14-11ec-883b-c61df66c07e7/kops create cluster --name e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.2.0_HVM-20210907-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.123.225.205/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-2a --master-size c5.large
I0923 02:17:35.788249    4710 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 02:17:35.788380    4710 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0923 02:17:35.816815    4710 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0923 02:17:36.592225    4710 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0923 02:17:59.336069    4669 up.go:181] /logs/artifacts/365c0273-1c14-11ec-883b-c61df66c07e7/kops validate cluster --name e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0923 02:17:59.354105    4730 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 02:17:59.354230    4730 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io

W0923 02:18:00.336165    4730 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0923 02:18:10.372364    4730 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0923 02:18:20.402993    4730 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
W0923 02:18:30.444252    4730 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
W0923 02:18:40.490861    4730 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
W0923 02:18:50.536920    4730 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
W0923 02:19:00.567314    4730 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
W0923 02:19:10.598835    4730 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
W0923 02:19:20.637436    4730 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
W0923 02:19:30.682675    4730 validate_cluster.go:232] (will retry): cluster not yet healthy
W0923 02:19:40.716142    4730 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0923 02:19:50.750749    4730 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
W0923 02:20:00.796936    4730 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
W0923 02:20:10.864419    4730 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
W0923 02:20:20.899103    4730 validate_cluster.go:232] (will retry): cluster not yet healthy
W0923 02:20:30.959470    4730 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0923 02:20:40.996604    4730 validate_cluster.go:232] (will retry): cluster not yet healthy
W0923 02:20:51.042205    4730 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-2a	Master	c5.large	1	1	us-east-2a
nodes-us-east-2a	Node	t3.medium	4	4	us-east-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0923 02:21:01.104546    4730 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
W0923 02:21:11.142142    4730 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
W0923 02:21:21.176319    4730 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
W0923 02:21:31.223999    4730 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
W0923 02:21:41.256003    4730 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
W0923 02:21:51.287331    4730 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
W0923 02:22:01.337037    4730 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
W0923 02:22:11.384467    4730 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
W0923 02:22:21.450318    4730 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
W0923 02:22:31.479307    4730 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
W0923 02:22:41.524356    4730 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
W0923 02:22:51.556330    4730 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
W0923 02:23:01.606808    4730 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
W0923 02:23:11.653627    4730 validate_cluster.go:232] (will retry): cluster not yet healthy
W0923 02:23:51.691373    4730 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
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
... skipping 8 lines ...
Machine	i-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:24:03.083057    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:24:14.023250    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:24:24.879210    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:24:35.774934    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:24:46.671400    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:24:57.767666    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:25:08.701422    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:25:19.619476    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:25:30.541616    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:25:41.547254    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:25:52.551856    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:26:03.526235    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:26:14.727040    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:26:25.708179    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:26:36.624780    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:26:47.654697    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:26:58.679517    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:27:09.627013    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:27:20.436399    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:27:31.408973    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:27:42.326588    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:27:53.405742    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:28:04.293114    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:28:15.192252    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:28:26.081050    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:28:36.990046    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:28:47.914695    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:28:58.850348    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:29:09.746988    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:29:20.654906    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:29:31.697189    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:29:42.575871    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:29:53.398765    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:30:04.383997    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:30:15.580811    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:30:26.524800    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:30:37.408639    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:30:48.310066    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:30:59.202769    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:31:10.106192    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:31:21.120303    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:31:31.989929    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:31:42.922840    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:31:53.919537    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:32:04.910117    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:32:15.917161    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:32:27.055462    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:32:37.956547    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:32:48.827722    4730 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-0eed6c5be23a9e539				machine "i-0eed6c5be23a9e539" has not yet joined cluster
Node	ip-172-20-53-154.us-east-2.compute.internal	node "ip-172-20-53-154.us-east-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x6pxj			system-node-critical pod "cilium-x6pxj" is pending
Pod	kube-system/coredns-5dc785954d-hx2tb		system-cluster-critical pod "coredns-5dc785954d-hx2tb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-2xsc7	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-2xsc7" is pending

Validation Failed
W0923 02:32:59.698342    4730 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0923 02:33:09.708073    4669 dumplogs.go:40] /logs/artifacts/365c0273-1c14-11ec-883b-c61df66c07e7/kops toolbox dump --name e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0923 02:33:09.727294    4741 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 02:33:09.727411    4741 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/23 02:33:15 Dumping node ip-172-20-53-154.us-east-2.compute.internal
2021/09/23 02:33:17 dumping node not registered in kubernetes: 18.119.122.48
2021/09/23 02:33:17 Dumping node 18.119.122.48
... skipping 1277 lines ...
route-table:rtb-0e139a03b8ca659ab	ok
vpc:vpc-0951b56a159dc5964	ok
dhcp-options:dopt-07c6c30b70aef76dc	ok
Deleted kubectl config for e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io

Deleted cluster: "e2e-70d4c15d8d-7012d.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace