This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-08-20 03:40
Elapsed18m2s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0820 03:41:38.611696    4073 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0820 03:41:38.613252    4073 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.22.0-alpha.3+v1.22.0-alpha.2-245-g8b04759218/linux/amd64/kops
I0820 03:41:39.387221    4073 up.go:43] Cleaning up any leaked resources from previous cluster
I0820 03:41:39.387266    4073 dumplogs.go:38] /logs/artifacts/52a170f8-0168-11ec-bd43-2ed83b96fba5/kops toolbox dump --name e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0820 03:41:39.407058    4091 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0820 03:41:39.407183    4091 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io" not found
W0820 03:41:39.936282    4073 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0820 03:41:39.936389    4073 down.go:48] /logs/artifacts/52a170f8-0168-11ec-bd43-2ed83b96fba5/kops delete cluster --name e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io --yes
I0820 03:41:39.957051    4101 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0820 03:41:39.957176    4101 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io" not found
I0820 03:41:40.433864    4073 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/08/20 03:41:40 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
I0820 03:41:40.441976    4073 http.go:37] curl https://ip.jsb.workers.dev
I0820 03:41:40.541517    4073 up.go:144] /logs/artifacts/52a170f8-0168-11ec-bd43-2ed83b96fba5/kops create cluster --name e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.14 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.3_HVM-20210209-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.72.170.46/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-1a --master-size c5.large
I0820 03:41:40.559705    4112 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0820 03:41:40.560099    4112 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
I0820 03:41:40.586766    4112 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0820 03:41:41.260212    4112 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0820 03:42:04.330551    4073 up.go:181] /logs/artifacts/52a170f8-0168-11ec-bd43-2ed83b96fba5/kops validate cluster --name e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0820 03:42:04.350630    4132 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0820 03:42:04.350772    4132 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io

W0820 03:42:05.382106    4132 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-deb8a118c5-c99a5.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
W0820 03:42:15.422861    4132 validate_cluster.go:232] (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
W0820 03:42:25.491630    4132 validate_cluster.go:232] (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
W0820 03:42:35.533154    4132 validate_cluster.go:232] (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
W0820 03:42:45.586814    4132 validate_cluster.go:232] (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
W0820 03:42:55.635715    4132 validate_cluster.go:232] (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
W0820 03:43:05.680400    4132 validate_cluster.go:232] (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
W0820 03:43:15.725380    4132 validate_cluster.go:232] (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
W0820 03:43:25.766283    4132 validate_cluster.go:232] (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
W0820 03:43:35.804575    4132 validate_cluster.go:232] (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
W0820 03:43:45.842928    4132 validate_cluster.go:232] (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
W0820 03:43:55.877161    4132 validate_cluster.go:232] (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
W0820 03:44:05.925215    4132 validate_cluster.go:232] (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
W0820 03:44:15.959250    4132 validate_cluster.go:232] (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
W0820 03:44:26.006138    4132 validate_cluster.go:232] (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
W0820 03:44:36.042342    4132 validate_cluster.go:232] (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
W0820 03:44:46.087287    4132 validate_cluster.go:232] (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
W0820 03:44:56.120085    4132 validate_cluster.go:232] (will retry): cluster not yet healthy
W0820 03:45:06.139661    4132 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0820 03:45:16.172774    4132 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-deb8a118c5-c99a5.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
W0820 03:45:26.209677    4132 validate_cluster.go:232] (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
W0820 03:45:36.302623    4132 validate_cluster.go:232] (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
W0820 03:45:46.329225    4132 validate_cluster.go:232] (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
W0820 03:45:56.364115    4132 validate_cluster.go:232] (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
W0820 03:46:06.402389    4132 validate_cluster.go:232] (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
W0820 03:46:16.452797    4132 validate_cluster.go:232] (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
W0820 03:46:26.487782    4132 validate_cluster.go:232] (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
W0820 03:46:36.518557    4132 validate_cluster.go:232] (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
W0820 03:46:46.557713    4132 validate_cluster.go:232] (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
W0820 03:46:56.594803    4132 validate_cluster.go:232] (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
W0820 03:47:06.628280    4132 validate_cluster.go:232] (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
W0820 03:47:16.666786    4132 validate_cluster.go:232] (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
W0820 03:47:26.704934    4132 validate_cluster.go:232] (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
W0820 03:47:36.742086    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:47:48.403967    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:47:59.569801    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:48:10.741411    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:48:21.949166    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:48:33.188682    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:48:44.626380    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:48:55.764596    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:49:06.940789    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:49:18.314424    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:49:29.506834    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:49:40.733703    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:49:51.907258    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:50:03.176998    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:50:14.400545    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:50:25.659527    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:50:36.984275    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:50:48.133170    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:50:59.330492    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:51:10.496827    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:51:21.621325    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:51:32.862020    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:51:44.231157    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:51:55.725002    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:52:06.951608    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:52:18.200978    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:52:29.375076    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:52:40.528235    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:52:51.692638    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:53:02.800410    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:53:14.063895    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:53:25.263933    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:53:36.462936    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:53:47.633769    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:53:58.809341    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:54:09.997765    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:54:21.177033    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:54:32.363529    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:54:44.507708    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:54:55.596545    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:55:06.933428    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:55:18.102948    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:55:29.314121    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:55:40.759119    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:55:51.998661    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:56:03.341495    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:56:14.543577    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:56:25.712028    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:56:37.077910    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:56:48.287121    4132 validate_cluster.go:232] (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-071d646e44400024a					machine "i-071d646e44400024a" has not yet joined cluster
Node	ip-172-20-32-16.us-west-1.compute.internal		node "ip-172-20-32-16.us-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-zwhhf				system-node-critical pod "cilium-zwhhf" is pending
Pod	kube-system/kube-dns-696cb84c7-6rg4x			system-cluster-critical pod "kube-dns-696cb84c7-6rg4x" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-q2hhl	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-q2hhl" is pending

Validation Failed
W0820 03:56:59.762564    4132 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0820 03:57:09.768569    4073 dumplogs.go:38] /logs/artifacts/52a170f8-0168-11ec-bd43-2ed83b96fba5/kops toolbox dump --name e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0820 03:57:09.789839    4145 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0820 03:57:09.790026    4145 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
2021/08/20 03:57:17 Dumping node ip-172-20-32-16.us-west-1.compute.internal
2021/08/20 03:57:19 dumping node not registered in kubernetes: 54.193.26.150
2021/08/20 03:57:19 Dumping node 54.193.26.150
... skipping 1244 lines ...
route-table:rtb-0a791b1d7cd9fbc13	ok
vpc:vpc-0acd07b3fd158bdc2	ok
dhcp-options:dopt-09b53e96fc98e2c7a	ok
Deleted kubectl config for e2e-deb8a118c5-c99a5.test-cncf-aws.k8s.io

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