This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-21 01:08
Elapsed20m5s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I0921 01:09:05.960560    4666 up.go:43] Cleaning up any leaked resources from previous cluster
I0921 01:09:05.960596    4666 dumplogs.go:40] /logs/artifacts/50e88b34-1a78-11ec-8e49-8acb7ceab3aa/kops toolbox dump --name e2e-ef1cb24276-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0921 01:09:05.976887    4686 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0921 01:09:05.976970    4686 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-ef1cb24276-99215.test-cncf-aws.k8s.io" not found
W0921 01:09:06.467933    4666 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0921 01:09:06.468015    4666 down.go:48] /logs/artifacts/50e88b34-1a78-11ec-8e49-8acb7ceab3aa/kops delete cluster --name e2e-ef1cb24276-99215.test-cncf-aws.k8s.io --yes
I0921 01:09:06.483033    4696 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0921 01:09:06.483119    4696 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-ef1cb24276-99215.test-cncf-aws.k8s.io" not found
I0921 01:09:07.055391    4666 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/21 01:09:07 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
I0921 01:09:07.063280    4666 http.go:37] curl https://ip.jsb.workers.dev
I0921 01:09:07.234256    4666 up.go:144] /logs/artifacts/50e88b34-1a78-11ec-8e49-8acb7ceab3aa/kops create cluster --name e2e-ef1cb24276-99215.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=calico --container-runtime=containerd --admin-access 34.123.251.80/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-1a --master-size c5.large
I0921 01:09:07.251326    4706 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0921 01:09:07.251420    4706 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0921 01:09:07.296629    4706 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0921 01:09:07.831683    4706 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I0921 01:09:34.525151    4666 up.go:181] /logs/artifacts/50e88b34-1a78-11ec-8e49-8acb7ceab3aa/kops validate cluster --name e2e-ef1cb24276-99215.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0921 01:09:34.540863    4725 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0921 01:09:34.540956    4725 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ef1cb24276-99215.test-cncf-aws.k8s.io

W0921 01:09:36.145220    4725 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ef1cb24276-99215.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
W0921 01:09:46.177173    4725 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
W0921 01:09:56.242326    4725 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
W0921 01:10:06.273289    4725 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
W0921 01:10:16.304981    4725 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
W0921 01:10:26.340726    4725 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
W0921 01:10:36.375650    4725 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
W0921 01:10:46.411757    4725 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
W0921 01:10:56.490236    4725 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
W0921 01:11:06.533969    4725 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
W0921 01:11:16.562754    4725 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
W0921 01:11:26.609876    4725 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
W0921 01:11:36.653968    4725 validate_cluster.go:221] (will retry): cluster not yet healthy
W0921 01:11:46.682905    4725 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ef1cb24276-99215.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
W0921 01:11:56.714234    4725 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
W0921 01:12:06.742924    4725 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
W0921 01:12:16.773520    4725 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
W0921 01:12:26.806588    4725 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
W0921 01:12:36.875792    4725 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
W0921 01:12:46.911979    4725 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
W0921 01:12:56.947783    4725 validate_cluster.go:221] (will retry): cluster not yet healthy
W0921 01:13:06.967015    4725 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ef1cb24276-99215.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0921 01:13:16.987654    4725 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ef1cb24276-99215.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
W0921 01:13:27.023643    4725 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
W0921 01:13:37.058687    4725 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
W0921 01:13:47.095074    4725 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
W0921 01:13:57.127861    4725 validate_cluster.go:221] (will retry): cluster not yet healthy
W0921 01:14:07.150546    4725 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ef1cb24276-99215.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
W0921 01:14:17.182403    4725 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
W0921 01:14:27.215978    4725 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
W0921 01:14:37.394127    4725 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 12 lines ...
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-qfhdl				system-node-critical pod "calico-node-qfhdl" is pending
Pod	kube-system/calico-node-vzqdl				system-node-critical pod "calico-node-vzqdl" is pending
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-4lm4q		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-4lm4q" is pending

Validation Failed
W0921 01:14:50.221573    4725 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 10 lines ...
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-qfhdl				system-node-critical pod "calico-node-qfhdl" is not ready (calico-node)
Pod	kube-system/calico-node-vzqdl				system-node-critical pod "calico-node-vzqdl" is not ready (calico-node)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-4lm4q		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-4lm4q" is pending

Validation Failed
W0921 01:15:02.264807    4725 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 14 lines ...
Pod	kube-system/calico-node-j7v6k				system-node-critical pod "calico-node-j7v6k" is pending
Pod	kube-system/calico-node-qfhdl				system-node-critical pod "calico-node-qfhdl" is not ready (calico-node)
Pod	kube-system/calico-node-vzqdl				system-node-critical pod "calico-node-vzqdl" is not ready (calico-node)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is pending
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:15:14.191192    4725 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 13 lines ...
Pod	kube-system/coredns-5dc785954d-9xjhc					system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8					system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-53-91.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-53-91.eu-west-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-54-38.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-38.eu-west-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-42.eu-west-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-42.eu-west-1.compute.internal" is pending

Validation Failed
W0921 01:15:26.435792    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:15:38.450401    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:15:50.571126    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:16:02.537241    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:16:14.558375    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:16:26.510945    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:16:38.476603    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:16:50.299667    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:17:02.304127    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:17:14.266220    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:17:26.500350    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:17:38.500955    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:17:50.423453    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:18:02.473853    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:18:14.523678    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:18:26.558269    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:18:38.548462    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:18:50.856219    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:19:02.739375    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:19:14.631959    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:19:26.507069    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:19:38.402564    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:19:50.217198    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:20:02.620513    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:20:14.582624    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:20:26.524482    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:20:38.489080    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:20:50.406638    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:21:02.432247    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:21:14.357969    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:21:26.426935    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:21:38.415693    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:21:50.445329    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:22:02.303342    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:22:14.242895    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:22:26.179980    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:22:38.094788    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:22:50.516727    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:23:02.617684    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:23:14.533012    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:23:26.675235    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:23:38.591091    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:23:50.576237    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:24:02.545192    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:24:14.471294    4725 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-6vgz4	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-6vgz4" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-9xjhc			system-cluster-critical pod "coredns-5dc785954d-9xjhc" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-xvsv8			system-cluster-critical pod "coredns-5dc785954d-xvsv8" is not ready (coredns)

Validation Failed
W0921 01:24:26.385030    4725 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0921 01:24:36.394902    4666 dumplogs.go:40] /logs/artifacts/50e88b34-1a78-11ec-8e49-8acb7ceab3aa/kops toolbox dump --name e2e-ef1cb24276-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0921 01:24:36.415060    4735 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0921 01:24:36.415187    4735 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/21 01:24:46 Dumping node ip-172-20-40-101.eu-west-1.compute.internal
2021/09/21 01:24:51 Dumping node ip-172-20-41-155.eu-west-1.compute.internal
2021/09/21 01:24:55 Dumping node ip-172-20-53-91.eu-west-1.compute.internal
... skipping 1449 lines ...
route-table:rtb-0c2ee628d5d7f5d48	ok
vpc:vpc-074b634a0964b9eaa	ok
dhcp-options:dopt-0b6bffd939bd7ff13	ok
Deleted kubectl config for e2e-ef1cb24276-99215.test-cncf-aws.k8s.io

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