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

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I0923 12:03:58.996469    4656 up.go:43] Cleaning up any leaked resources from previous cluster
I0923 12:03:58.996523    4656 dumplogs.go:40] /logs/artifacts/25dfd451-1c66-11ec-883b-c61df66c07e7/kops toolbox dump --name e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0923 12:03:59.012689    4674 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0923 12:03:59.012791    4674 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io" not found
W0923 12:03:59.496942    4656 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0923 12:03:59.496998    4656 down.go:48] /logs/artifacts/25dfd451-1c66-11ec-883b-c61df66c07e7/kops delete cluster --name e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io --yes
I0923 12:03:59.511963    4684 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0923 12:03:59.512049    4684 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io" not found
I0923 12:03:59.970706    4656 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/23 12:03:59 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
I0923 12:03:59.977688    4656 http.go:37] curl https://ip.jsb.workers.dev
I0923 12:04:00.031253    4656 up.go:144] /logs/artifacts/25dfd451-1c66-11ec-883b-c61df66c07e7/kops create cluster --name e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.2.0_HVM-20210907-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.134.168.93/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-1a --master-size c5.large
I0923 12:04:00.050157    4694 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0923 12:04:00.050289    4694 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0923 12:04:00.095781    4694 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0923 12:04:00.655549    4694 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I0923 12:04:27.332856    4656 up.go:181] /logs/artifacts/25dfd451-1c66-11ec-883b-c61df66c07e7/kops validate cluster --name e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0923 12:04:27.351196    4713 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0923 12:04:27.351871    4713 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io

W0923 12:04:28.725054    4713 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7351f4aefd-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-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
W0923 12:04:38.759528    4713 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
W0923 12:04:48.804979    4713 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
W0923 12:04:58.845177    4713 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
W0923 12:05:08.896195    4713 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
W0923 12:05:18.925903    4713 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
W0923 12:05:29.003190    4713 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
W0923 12:05:39.033411    4713 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
W0923 12:05:49.064262    4713 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
W0923 12:05:59.096853    4713 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
W0923 12:06:09.142398    4713 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
W0923 12:06:19.189283    4713 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
W0923 12:06:29.235944    4713 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
W0923 12:06:39.270975    4713 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
W0923 12:06:49.351609    4713 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
W0923 12:06:59.388058    4713 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
W0923 12:07:09.532766    4713 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
W0923 12:07:19.575103    4713 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
W0923 12:07:29.609531    4713 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
W0923 12:07:39.656818    4713 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
W0923 12:07:49.687427    4713 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
W0923 12:07:59.734630    4713 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
W0923 12:08:09.781620    4713 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
W0923 12:08:19.822583    4713 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
W0923 12:08:29.858510    4713 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
W0923 12:08:39.889341    4713 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
W0923 12:08:49.917586    4713 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
W0923 12:08:59.984327    4713 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
W0923 12:09:10.019080    4713 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
W0923 12:09:20.053010    4713 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
W0923 12:09:30.086294    4713 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
W0923 12:09:40.338537    4713 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
W0923 12:09:50.369069    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:10:03.433419    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:10:15.422720    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:10:27.520252    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:10:40.499224    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:10:52.471972    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:11:04.311185    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:11:16.292192    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:11:28.199322    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:11:40.214792    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:11:52.092170    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:12:04.058785    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:12:15.873932    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:12:27.842404    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:12:39.803269    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:12:51.736282    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:13:03.680135    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:13:15.672699    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:13:27.556397    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:13:39.488967    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:13:51.285492    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:14:03.632282    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:14:15.604839    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:14:27.563880    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:14:39.533992    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:14:51.426601    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:15:03.467971    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:15:15.441580    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:15:27.394706    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:15:39.248425    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:15:51.159821    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:16:03.176954    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:16:15.137322    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:16:27.039227    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:16:38.948225    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:16:50.877928    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:17:02.902860    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:17:14.826174    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:17:26.767466    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:17:38.705091    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:17:50.615516    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:18:02.984491    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:18:14.772194    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:18:26.689546    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:18:38.655143    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:18:50.540626    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:19:02.406554    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:19:14.293068    4713 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-0ca3a551eb0ef5f60				machine "i-0ca3a551eb0ef5f60" has not yet joined cluster
Node	ip-172-20-32-252.eu-west-1.compute.internal	node "ip-172-20-32-252.eu-west-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lprgk			system-node-critical pod "cilium-lprgk" is pending
Pod	kube-system/coredns-64497985bd-pmtbv		system-cluster-critical pod "coredns-64497985bd-pmtbv" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-kzthh	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-kzthh" is pending

Validation Failed
W0923 12:19:26.166863    4713 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0923 12:19:36.178174    4656 dumplogs.go:40] /logs/artifacts/25dfd451-1c66-11ec-883b-c61df66c07e7/kops toolbox dump --name e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0923 12:19:36.196422    4723 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0923 12:19:36.196562    4723 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/23 12:19:46 Dumping node ip-172-20-32-252.eu-west-1.compute.internal
2021/09/23 12:19:51 dumping node not registered in kubernetes: 34.245.199.86
2021/09/23 12:19:51 Dumping node 34.245.199.86
... skipping 1235 lines ...
route-table:rtb-0f311e8604d2b1cf3	ok
vpc:vpc-041d3aebf9465841e	ok
dhcp-options:dopt-0fea86650c7d1c77e	ok
Deleted kubectl config for e2e-7351f4aefd-773a8.test-cncf-aws.k8s.io

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