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

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0813 03:42:31.606496    4107 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0813 03:42:31.608086    4107 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.22.0-alpha.3+v1.22.0-alpha.2-196-gb1e6064501/linux/amd64/kops
I0813 03:42:32.772361    4107 up.go:43] Cleaning up any leaked resources from previous cluster
I0813 03:42:32.772406    4107 dumplogs.go:38] /logs/artifacts/41a21ec2-fbe8-11eb-9eab-220dac5d1fa2/kops toolbox dump --name e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0813 03:42:32.805751    4129 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0813 03:42:32.805858    4129 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io" not found
W0813 03:42:33.336264    4107 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0813 03:42:33.336456    4107 down.go:48] /logs/artifacts/41a21ec2-fbe8-11eb-9eab-220dac5d1fa2/kops delete cluster --name e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io --yes
I0813 03:42:33.358762    4139 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0813 03:42:33.358884    4139 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io" not found
I0813 03:42:33.842467    4107 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/08/13 03:42:33 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
I0813 03:42:33.853988    4107 http.go:37] curl https://ip.jsb.workers.dev
I0813 03:42:33.941780    4107 up.go:144] /logs/artifacts/41a21ec2-fbe8-11eb-9eab-220dac5d1fa2/kops create cluster --name e2e-7a5b10a624-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.134.223.73/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-1a --master-size c5.large
I0813 03:42:33.964438    4148 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0813 03:42:33.964561    4148 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
I0813 03:42:34.004699    4148 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0813 03:42:34.601578    4148 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0813 03:43:01.243837    4107 up.go:181] /logs/artifacts/41a21ec2-fbe8-11eb-9eab-220dac5d1fa2/kops validate cluster --name e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0813 03:43:01.274037    4166 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0813 03:43:01.274140    4166 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io

W0813 03:43:02.660201    4166 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0813 03:43:12.697058    4166 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:43:22.726072    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:43:32.889797    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:43:42.920274    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:43:52.954716    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:44:02.996851    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:44:13.044341    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:44:23.086856    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:44:33.134617    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:44:43.165254    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
W0813 03:44:53.179702    4166 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:45:03.211178    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:45:13.297494    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:45:23.330537    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:45:33.374326    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
W0813 03:45:43.405266    4166 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:45:53.439166    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:46:03.470148    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
W0813 03:46:13.486446    4166 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:46:23.547759    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:46:33.624669    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:46:43.668680    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:46:53.697018    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:47:03.727983    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:47:13.769986    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:47:23.798825    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:47:33.831633    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:47:43.861977    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
W0813 03:47:53.893414    4166 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:48:03.922549    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:48:13.964877    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:48:23.995650    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:48:34.024066    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:48:44.077015    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-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
W0813 03:48:54.108797    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
W0813 03:49:34.139437    4166 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

NODE STATUS
... skipping 8 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:49:46.912158    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:49:58.753120    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:50:10.595031    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:50:22.500400    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:50:34.323662    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:50:46.168410    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:50:58.036910    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:51:09.890158    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:51:21.840584    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:51:33.707766    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:51:45.636934    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:51:57.481559    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:52:09.384037    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:52:21.304976    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:52:33.248740    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:52:45.097653    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:52:57.180333    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:53:09.116299    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:53:21.027712    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:53:32.888698    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:53:45.193829    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:53:57.191265    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:54:09.040588    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:54:20.992134    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:54:32.992144    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:54:45.047900    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:54:56.928169    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:55:09.965781    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:55:21.825423    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:55:33.736872    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:55:45.714302    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:55:57.663073    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:56:09.538043    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:56:21.592319    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:56:33.507136    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:56:45.455397    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:56:57.331531    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:57:09.208237    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:57:21.112819    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:57:33.015008    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:57:45.343896    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	4	4	eu-west-1a

... skipping 9 lines ...
Machine	i-0cf28d8cc8257944f					machine "i-0cf28d8cc8257944f" has not yet joined cluster
Node	ip-172-20-47-197.eu-west-1.compute.internal		node "ip-172-20-47-197.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-58vxt				system-node-critical pod "cilium-58vxt" is pending
Pod	kube-system/kube-dns-696cb84c7-dth4n			system-cluster-critical pod "kube-dns-696cb84c7-dth4n" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-9nw4j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-9nw4j" is pending

Validation Failed
W0813 03:57:57.274877    4166 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0813 03:58:07.281795    4107 dumplogs.go:38] /logs/artifacts/41a21ec2-fbe8-11eb-9eab-220dac5d1fa2/kops toolbox dump --name e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0813 03:58:07.305116    4177 featureflag.go:173] FeatureFlag "SpecOverrideFlag"=true
I0813 03:58:07.305385    4177 featureflag.go:173] FeatureFlag "AlphaAllowGCE"=true
2021/08/13 03:58:17 Dumping node ip-172-20-47-197.eu-west-1.compute.internal
2021/08/13 03:58:22 dumping node not registered in kubernetes: 3.249.227.9
2021/08/13 03:58:22 Dumping node 3.249.227.9
... skipping 1196 lines ...
route-table:rtb-056f2fdc13feac1fb	ok
vpc:vpc-0896009d322602f72	ok
dhcp-options:dopt-001bd6b0e6dcedb13	ok
Deleted kubectl config for e2e-7a5b10a624-c99a5.test-cncf-aws.k8s.io

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