This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-19 09:24
Elapsed17m49s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0919 09:25:20.669495    4087 up.go:43] Cleaning up any leaked resources from previous cluster
I0919 09:25:20.669533    4087 dumplogs.go:38] /logs/artifacts/5116e026-192b-11ec-bfa0-9e8ae4027703/kops toolbox dump --name e2e-fea013dbeb-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0919 09:25:20.685546    4108 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0919 09:25:20.685655    4108 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-fea013dbeb-53349.test-cncf-aws.k8s.io" not found
W0919 09:25:21.209327    4087 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0919 09:25:21.209379    4087 down.go:48] /logs/artifacts/5116e026-192b-11ec-bfa0-9e8ae4027703/kops delete cluster --name e2e-fea013dbeb-53349.test-cncf-aws.k8s.io --yes
I0919 09:25:21.225137    4118 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0919 09:25:21.225231    4118 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-fea013dbeb-53349.test-cncf-aws.k8s.io" not found
I0919 09:25:22.157019    4087 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/19 09:25:22 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
I0919 09:25:22.164840    4087 http.go:37] curl https://ip.jsb.workers.dev
I0919 09:25:22.443180    4087 up.go:144] /logs/artifacts/5116e026-192b-11ec-bfa0-9e8ae4027703/kops create cluster --name e2e-fea013dbeb-53349.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.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 146.148.58.30/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0919 09:25:22.459949    4129 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0919 09:25:22.460169    4129 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0919 09:25:22.507423    4129 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0919 09:25:23.023520    4129 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I0919 09:25:48.567048    4087 up.go:181] /logs/artifacts/5116e026-192b-11ec-bfa0-9e8ae4027703/kops validate cluster --name e2e-fea013dbeb-53349.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0919 09:25:48.583695    4149 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0919 09:25:48.583823    4149 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-fea013dbeb-53349.test-cncf-aws.k8s.io

W0919 09:25:49.675983    4149 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fea013dbeb-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0919 09:25:59.725013    4149 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fea013dbeb-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:26:09.760288    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:26:19.790785    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:26:29.835091    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:26:39.881348    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:26:49.923134    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:26:59.954537    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:27:09.983220    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:27:20.013428    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:27:30.065355    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:27:40.098307    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
W0919 09:27:50.135394    4149 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fea013dbeb-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:28:00.166083    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:28:10.198260    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:28:20.231637    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:28:30.263417    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:28:40.300129    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:28:50.368340    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:29:00.404831    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:29:10.435695    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:29:20.481706    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:29:30.514803    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:29:40.543980    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:29:50.575936    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:30:00.612524    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:30:10.651512    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

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
W0919 09:30:20.682250    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:30:32.304538    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:30:43.582893    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:30:54.890824    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:31:06.327687    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:31:17.506952    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:31:28.646745    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:31:39.881981    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:31:51.040077    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:32:02.251663    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:32:13.510295    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:32:24.758129    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:32:35.907566    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:32:47.117154    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:32:58.422978    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:33:09.668582    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:33:20.934711    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:33:32.049061    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:33:43.235924    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:33:54.460363    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:34:05.607263    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:34:16.805267    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:34:28.471991    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:34:39.683170    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:34:50.963697    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:35:02.206916    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:35:13.386859    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:35:24.648573    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:35:35.877206    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:35:47.091243    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:35:58.292681    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:36:09.442368    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:36:20.703965    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:36:31.927174    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:36:43.127160    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:36:54.473266    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:37:05.745855    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:37:17.071016    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:37:28.817239    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:37:40.140152    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:37:51.635798    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:38:02.887526    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:38:14.068923    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:38:25.490228    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:38:36.759588    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:38:47.927922    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:38:59.228056    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:39:10.403979    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:39:21.597918    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:39:32.802213    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:39:43.948481    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:39:55.137970    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:40:06.414831    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:40:17.619491    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:40:28.818371    4149 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-1a	Master	c5.large	1	1	us-west-1a
nodes-us-west-1a	Node	t3.medium	4	4	us-west-1a

... skipping 9 lines ...
Machine	i-0d078a5481a79e650				machine "i-0d078a5481a79e650" has not yet joined cluster
Node	ip-172-20-35-167.us-west-1.compute.internal	node "ip-172-20-35-167.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-62lhh			system-node-critical pod "cilium-62lhh" is pending
Pod	kube-system/coredns-5dc785954d-gsvn5		system-cluster-critical pod "coredns-5dc785954d-gsvn5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vbssb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vbssb" is pending

Validation Failed
W0919 09:40:40.032456    4149 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0919 09:40:50.039288    4087 dumplogs.go:38] /logs/artifacts/5116e026-192b-11ec-bfa0-9e8ae4027703/kops toolbox dump --name e2e-fea013dbeb-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0919 09:40:50.055972    4160 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0919 09:40:50.056083    4160 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/19 09:40:57 Dumping node ip-172-20-35-167.us-west-1.compute.internal
2021/09/19 09:41:00 dumping node not registered in kubernetes: 52.53.202.126
2021/09/19 09:41:00 Dumping node 52.53.202.126
... skipping 1209 lines ...
route-table:rtb-0e65af98717fe293e	ok
vpc:vpc-006d20d6523237ee6	ok
dhcp-options:dopt-007a14659184d96e2	ok
Deleted kubectl config for e2e-fea013dbeb-53349.test-cncf-aws.k8s.io

Deleted cluster: "e2e-fea013dbeb-53349.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace