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

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0909 12:03:42.729498    4099 up.go:43] Cleaning up any leaked resources from previous cluster
I0909 12:03:42.729535    4099 dumplogs.go:38] /logs/artifacts/c5cdeec7-1165-11ec-bf73-ae50abde5ff3/kops toolbox dump --name e2e-944a633e05-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0909 12:03:42.748640    4122 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0909 12:03:42.748816    4122 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-944a633e05-773a8.test-cncf-aws.k8s.io" not found
W0909 12:03:43.277447    4099 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0909 12:03:43.277525    4099 down.go:48] /logs/artifacts/c5cdeec7-1165-11ec-bf73-ae50abde5ff3/kops delete cluster --name e2e-944a633e05-773a8.test-cncf-aws.k8s.io --yes
I0909 12:03:43.295751    4132 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0909 12:03:43.296062    4132 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-944a633e05-773a8.test-cncf-aws.k8s.io" not found
I0909 12:03:43.824223    4099 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/09 12:03:43 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
I0909 12:03:43.833806    4099 http.go:37] curl https://ip.jsb.workers.dev
I0909 12:03:43.921378    4099 up.go:144] /logs/artifacts/c5cdeec7-1165-11ec-bf73-ae50abde5ff3/kops create cluster --name e2e-944a633e05-773a8.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.10 --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 35.194.23.235/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-3a --master-size c5.large
I0909 12:03:43.940467    4142 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0909 12:03:43.940744    4142 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0909 12:03:43.989301    4142 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0909 12:03:44.550564    4142 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I0909 12:04:12.287305    4099 up.go:181] /logs/artifacts/c5cdeec7-1165-11ec-bf73-ae50abde5ff3/kops validate cluster --name e2e-944a633e05-773a8.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0909 12:04:12.312277    4162 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0909 12:04:12.312594    4162 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-944a633e05-773a8.test-cncf-aws.k8s.io

W0909 12:04:13.660906    4162 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-944a633e05-773a8.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0909 12:04:23.704734    4162 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-944a633e05-773a8.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-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:04:33.816073    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:04:43.846395    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:04:53.878546    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:05:04.034188    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:05:14.065449    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:05:24.107742    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:05:34.142746    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:05:44.173820    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:05:54.211252    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:06:04.244870    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:06:14.294473    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:06:24.415732    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:06:34.451417    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:06:44.488614    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:06:54.569221    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:07:04.601499    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:07:14.635516    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:07:24.773409    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:07:34.805540    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:07:44.842626    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:07:54.882299    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:08:04.993864    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:08:15.043349    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:08:25.273501    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:08:35.417561    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:08:45.451307    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:08:55.493251    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:09:05.656784    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:09:15.693822    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:09:25.760948    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:09:35.826914    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:09:45.863258    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:09:55.910346    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0909 12:10:05.946857    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:10:18.836279    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:10:31.065841    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:10:42.911284    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:10:54.783632    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:11:06.851968    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:11:18.810487    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:11:30.679879    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:11:42.500949    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:11:54.540859    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:12:06.471423    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:12:18.391501    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:12:30.316036    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:12:42.244451    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:12:54.190348    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:13:06.067682    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:13:17.995564    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:13:29.901429    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:13:41.907240    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:13:53.947198    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:14:06.015390    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:14:18.320486    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:14:30.236204    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:14:42.162092    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:14:54.054743    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:15:05.949057    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:15:17.871196    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:15:29.736557    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:15:41.742923    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:15:53.584914    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:16:05.450887    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:16:17.361196    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:16:29.200572    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:16:41.118609    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:16:53.010932    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:17:04.941267    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:17:16.941182    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:17:28.864237    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:17:40.788066    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:17:52.786975    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:18:04.704607    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:18:17.020087    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:18:28.941671    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:18:40.843925    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:18:52.738497    4162 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
Machine	i-0e6f815db24e78740				machine "i-0e6f815db24e78740" has not yet joined cluster
Node	ip-172-20-53-45.eu-west-3.compute.internal	node "ip-172-20-53-45.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-pprz4			system-node-critical pod "cilium-pprz4" is pending
Pod	kube-system/coredns-64497985bd-6bns5		system-cluster-critical pod "coredns-64497985bd-6bns5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-l5vx9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-l5vx9" is pending

Validation Failed
W0909 12:19:04.627940    4162 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0909 12:19:14.642138    4099 dumplogs.go:38] /logs/artifacts/c5cdeec7-1165-11ec-bf73-ae50abde5ff3/kops toolbox dump --name e2e-944a633e05-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0909 12:19:14.661998    4174 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0909 12:19:14.662140    4174 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/09 12:19:24 Dumping node ip-172-20-53-45.eu-west-3.compute.internal
2021/09/09 12:19:29 dumping node not registered in kubernetes: 15.237.119.10
2021/09/09 12:19:29 Dumping node 15.237.119.10
... skipping 1249 lines ...
route-table:rtb-0fd1870b3ad6d5196	ok
vpc:vpc-0b1c6249cee7558ca	ok
dhcp-options:dopt-09e0543d8468044be	ok
Deleted kubectl config for e2e-944a633e05-773a8.test-cncf-aws.k8s.io

Deleted cluster: "e2e-944a633e05-773a8.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace