This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-17 21:40
Elapsed18m56s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0917 21:41:20.261993    4075 up.go:43] Cleaning up any leaked resources from previous cluster
I0917 21:41:20.262026    4075 dumplogs.go:38] /logs/artifacts/cca0e9e6-17ff-11ec-bfa0-9e8ae4027703/kops toolbox dump --name e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0917 21:41:20.278851    4095 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0917 21:41:20.279007    4095 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io" not found
W0917 21:41:20.780368    4075 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0917 21:41:20.780432    4075 down.go:48] /logs/artifacts/cca0e9e6-17ff-11ec-bfa0-9e8ae4027703/kops delete cluster --name e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io --yes
I0917 21:41:20.795781    4106 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0917 21:41:20.795879    4106 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io" not found
I0917 21:41:21.350359    4075 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/17 21:41:21 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
I0917 21:41:21.358185    4075 http.go:37] curl https://ip.jsb.workers.dev
I0917 21:41:21.701767    4075 up.go:144] /logs/artifacts/cca0e9e6-17ff-11ec-bfa0-9e8ae4027703/kops create cluster --name e2e-88070d5e8c-8ebdc.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 --container-runtime=containerd --admin-access 34.121.205.196/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0917 21:41:21.719347    4116 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0917 21:41:21.719463    4116 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0917 21:41:21.764951    4116 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0917 21:41:22.440093    4116 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I0917 21:41:47.317355    4075 up.go:181] /logs/artifacts/cca0e9e6-17ff-11ec-bfa0-9e8ae4027703/kops validate cluster --name e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0917 21:41:47.333875    4137 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0917 21:41:47.333988    4137 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io

W0917 21:41:48.410994    4137 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0917 21:41:58.456286    4137 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-88070d5e8c-8ebdc.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
W0917 21:42:08.489403    4137 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
W0917 21:42:18.594988    4137 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
W0917 21:42:28.719470    4137 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
W0917 21:42:38.773635    4137 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
W0917 21:42:48.805299    4137 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
W0917 21:42:58.838031    4137 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
W0917 21:43:08.874152    4137 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
W0917 21:43:18.937666    4137 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
W0917 21:43:28.974585    4137 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
W0917 21:43:39.006904    4137 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
W0917 21:43:49.045156    4137 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
W0917 21:43:59.083485    4137 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
W0917 21:44:09.172443    4137 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
W0917 21:44:19.202934    4137 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
W0917 21:44:29.268803    4137 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
W0917 21:44:39.299406    4137 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
W0917 21:44:49.328677    4137 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
W0917 21:44:59.364071    4137 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
W0917 21:45:09.420585    4137 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
W0917 21:45:19.456418    4137 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
W0917 21:45:29.502594    4137 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
W0917 21:45:39.547569    4137 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
W0917 21:45:49.578672    4137 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
W0917 21:45:59.612801    4137 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
W0917 21:46:09.735812    4137 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
W0917 21:46:19.767128    4137 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
W0917 21:46:29.797622    4137 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
W0917 21:46:39.835335    4137 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
W0917 21:46:49.979131    4137 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
W0917 21:47:00.238708    4137 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
W0917 21:47:10.273480    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:47:21.985235    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:47:33.167122    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:47:44.332240    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:47:55.615481    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:48:06.804743    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:48:18.156533    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:48:29.357430    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:48:40.547425    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:48:51.779006    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:49:03.180975    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:49:14.369479    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:49:25.629408    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:49:36.783213    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:49:48.158418    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:49:59.435556    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:50:10.937263    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:50:22.165621    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:50:33.301925    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:50:44.469348    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:50:55.736799    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:51:06.936352    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:51:18.309539    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:51:29.529752    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:51:40.772251    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:51:51.967498    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:52:03.156268    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:52:14.330524    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:52:25.791138    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:52:37.127319    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:52:48.314003    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:52:59.587019    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:53:10.736169    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:53:21.982795    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:53:33.127158    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:53:44.274851    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:53:55.470796    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:54:06.955981    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:54:18.099531    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:54:29.303532    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:54:40.448371    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:54:51.654026    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:55:02.889654    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:55:14.377372    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:55:25.543322    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:55:36.755413    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:55:47.961062    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:55:59.158292    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:56:10.307699    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:56:21.526022    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:56:32.685120    4137 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-080cb04887f6d537c				machine "i-080cb04887f6d537c" has not yet joined cluster
Node	ip-172-20-39-207.us-west-1.compute.internal	node "ip-172-20-39-207.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-t7f5k			system-node-critical pod "cilium-t7f5k" is pending
Pod	kube-system/coredns-5dc785954d-rdlwq		system-cluster-critical pod "coredns-5dc785954d-rdlwq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfk6j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfk6j" is pending

Validation Failed
W0917 21:56:43.817416    4137 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0917 21:56:53.826831    4075 dumplogs.go:38] /logs/artifacts/cca0e9e6-17ff-11ec-bfa0-9e8ae4027703/kops toolbox dump --name e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0917 21:56:53.846449    4149 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0917 21:56:53.846709    4149 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/17 21:57:01 Dumping node ip-172-20-39-207.us-west-1.compute.internal
2021/09/17 21:57:03 dumping node not registered in kubernetes: 54.183.148.121
2021/09/17 21:57:03 Dumping node 54.183.148.121
... skipping 1305 lines ...
route-table:rtb-07e8e928a17f622ad	ok
vpc:vpc-0942b1a31967caf64	ok
dhcp-options:dopt-0445ebe238d0576c3	ok
Deleted kubectl config for e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io

Deleted cluster: "e2e-88070d5e8c-8ebdc.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace