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

No Test Failures!


Error lines from build-log.txt

... skipping 131 lines ...
I1017 09:24:46.279809    4693 up.go:43] Cleaning up any leaked resources from previous cluster
I1017 09:24:46.279840    4693 dumplogs.go:40] /logs/artifacts/e9a02a99-2f2b-11ec-8a05-6acfde499713/kops toolbox dump --name e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1017 09:24:46.289976    4714 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1017 09:24:46.290056    4714 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io" not found
W1017 09:24:46.813141    4693 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1017 09:24:46.813194    4693 down.go:48] /logs/artifacts/e9a02a99-2f2b-11ec-8a05-6acfde499713/kops delete cluster --name e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io --yes
I1017 09:24:46.825245    4724 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1017 09:24:46.825331    4724 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io" not found
I1017 09:24:47.350301    4693 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/17 09:24:47 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
I1017 09:24:47.360177    4693 http.go:37] curl https://ip.jsb.workers.dev
I1017 09:24:47.459566    4693 up.go:144] /logs/artifacts/e9a02a99-2f2b-11ec-8a05-6acfde499713/kops create cluster --name e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.232.169.255/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-1a --master-size c5.large
I1017 09:24:47.472741    4734 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1017 09:24:47.473055    4734 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1017 09:24:47.516456    4734 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1017 09:24:48.024631    4734 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1017 09:25:14.446226    4693 up.go:181] /logs/artifacts/e9a02a99-2f2b-11ec-8a05-6acfde499713/kops validate cluster --name e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1017 09:25:14.458726    4755 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1017 09:25:14.458806    4755 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io

W1017 09:25:15.826111    4755 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fe1cc1b9bb-53349.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
W1017 09:25:25.858767    4755 validate_cluster.go:221] (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
W1017 09:25:35.908500    4755 validate_cluster.go:221] (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
W1017 09:25:45.957231    4755 validate_cluster.go:221] (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
W1017 09:25:55.990701    4755 validate_cluster.go:221] (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
W1017 09:26:06.026814    4755 validate_cluster.go:221] (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
W1017 09:26:16.075207    4755 validate_cluster.go:221] (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
W1017 09:26:26.108433    4755 validate_cluster.go:221] (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
W1017 09:26:36.139736    4755 validate_cluster.go:221] (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
W1017 09:26:46.189836    4755 validate_cluster.go:221] (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
W1017 09:26:56.219792    4755 validate_cluster.go:221] (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
W1017 09:27:06.253157    4755 validate_cluster.go:221] (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
W1017 09:27:16.288947    4755 validate_cluster.go:221] (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
W1017 09:27:26.341453    4755 validate_cluster.go:221] (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
W1017 09:27:36.371787    4755 validate_cluster.go:221] (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
W1017 09:27:46.405728    4755 validate_cluster.go:221] (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
W1017 09:27:56.451485    4755 validate_cluster.go:221] (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
W1017 09:28:06.483705    4755 validate_cluster.go:221] (will retry): cluster not yet healthy
W1017 09:28:16.516839    4755 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fe1cc1b9bb-53349.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
W1017 09:28:26.548718    4755 validate_cluster.go:221] (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
W1017 09:28:36.580182    4755 validate_cluster.go:221] (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
W1017 09:28:46.627811    4755 validate_cluster.go:221] (will retry): cluster not yet healthy
W1017 09:28:56.654204    4755 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-fe1cc1b9bb-53349.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
W1017 09:29:06.687706    4755 validate_cluster.go:221] (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
W1017 09:29:16.756803    4755 validate_cluster.go:221] (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
W1017 09:29:26.792279    4755 validate_cluster.go:221] (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
W1017 09:29:36.822995    4755 validate_cluster.go:221] (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
W1017 09:29:46.867779    4755 validate_cluster.go:221] (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
W1017 09:29:56.911624    4755 validate_cluster.go:221] (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
W1017 09:30:06.943516    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:30:20.095699    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:30:32.319950    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:30:44.375331    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:30:56.768671    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:31:08.793959    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:31:20.844517    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:31:32.881270    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:31:44.926680    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:31:56.922202    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:32:08.969186    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:32:21.253821    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:32:33.327992    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:32:45.302180    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:32:57.412427    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:33:09.409146    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:33:21.255891    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:33:33.147891    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:33:45.091471    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:33:57.109587    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:34:09.446449    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:34:21.433287    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:34:33.484062    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:34:45.424036    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:34:58.499815    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:35:10.436583    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:35:22.304084    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:35:34.250455    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:35:46.112104    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:35:57.931206    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:36:09.944709    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:36:21.923011    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:36:33.897738    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:36:45.854500    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:36:57.807228    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:37:09.721387    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:37:21.711459    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:37:33.633883    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:37:46.463053    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:37:58.523357    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:38:10.801335    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:38:22.869106    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:38:34.859909    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:38:46.743328    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:38:58.723070    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:39:10.563338    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:39:22.740843    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:39:34.744886    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:39:46.653203    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:39:58.688688    4755 validate_cluster.go:221] (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-0cc719bbc081b91a5				machine "i-0cc719bbc081b91a5" has not yet joined cluster
Node	ip-172-20-38-15.eu-west-1.compute.internal	node "ip-172-20-38-15.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-df478			system-node-critical pod "cilium-df478" is pending
Pod	kube-system/coredns-5dc785954d-4x9vn		system-cluster-critical pod "coredns-5dc785954d-4x9vn" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-wx2ns	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-wx2ns" is pending

Validation Failed
W1017 09:40:10.653935    4755 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1017 09:40:20.658427    4693 dumplogs.go:40] /logs/artifacts/e9a02a99-2f2b-11ec-8a05-6acfde499713/kops toolbox dump --name e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1017 09:40:20.672575    4765 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1017 09:40:20.672795    4765 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/17 09:40:30 Dumping node ip-172-20-38-15.eu-west-1.compute.internal
2021/10/17 09:40:36 dumping node not registered in kubernetes: 52.49.184.212
2021/10/17 09:40:36 Dumping node 52.49.184.212
... skipping 1195 lines ...
route-table:rtb-0e98e1cc1676b0db8	ok
vpc:vpc-0017071d6da0877b7	ok
dhcp-options:dopt-0071f5dab6e0af643	ok
Deleted kubectl config for e2e-fe1cc1b9bb-53349.test-cncf-aws.k8s.io

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