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

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1008 21:40:59.277700    4877 up.go:43] Cleaning up any leaked resources from previous cluster
I1008 21:40:59.277728    4877 dumplogs.go:40] /logs/artifacts/30022cec-2880-11ec-b6b4-7efeba256487/kops toolbox dump --name e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1008 21:40:59.310256    4896 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1008 21:40:59.310395    4896 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io" not found
W1008 21:40:59.882132    4877 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1008 21:40:59.882203    4877 down.go:48] /logs/artifacts/30022cec-2880-11ec-b6b4-7efeba256487/kops delete cluster --name e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io --yes
I1008 21:40:59.912944    4907 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1008 21:40:59.913101    4907 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io" not found
I1008 21:41:00.429147    4877 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/08 21:41:00 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
I1008 21:41:00.438529    4877 http.go:37] curl https://ip.jsb.workers.dev
I1008 21:41:00.525505    4877 up.go:144] /logs/artifacts/30022cec-2880-11ec-b6b4-7efeba256487/kops create cluster --name e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=containerd --admin-access 35.222.171.231/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large
I1008 21:41:00.556056    4917 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1008 21:41:00.556155    4917 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1008 21:41:00.639576    4917 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1008 21:41:01.265864    4917 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I1008 21:41:28.105157    4877 up.go:181] /logs/artifacts/30022cec-2880-11ec-b6b4-7efeba256487/kops validate cluster --name e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1008 21:41:28.120803    4937 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1008 21:41:28.121563    4937 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io

W1008 21:41:29.403189    4937 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:41:39.446075    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:41:49.474866    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:41:59.534341    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:42:09.565414    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:42:19.599223    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:42:29.641255    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:42:39.671820    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:42:49.703505    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:42:59.733394    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:43:09.761562    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:43:19.790592    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:43:29.827093    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:43:39.869878    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:43:49.901895    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:43:59.935097    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:44:09.978853    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:44:20.026458    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:44:30.056744    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:44:40.091254    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:44:50.138753    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:45:00.171590    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:45:10.200342    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:45:20.229687    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:45:30.258303    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:45:40.289767    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:45:50.328711    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:46:00.385683    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:46:10.411608    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:46:20.448079    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:46:30.483508    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:46:40.518335    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-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
W1008 21:46:50.562695    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:47:03.410360    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:47:15.361154    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:47:27.302189    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:47:39.183983    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:47:51.096896    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:48:03.009508    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:48:14.930036    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:48:26.966608    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:48:38.967733    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:48:50.886336    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:49:02.838144    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:49:14.760945    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:49:26.693566    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:49:38.573866    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:49:50.514274    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:50:02.449281    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:50:14.353565    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:50:26.280737    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:50:38.246496    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:50:50.224189    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:51:02.610784    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:51:14.913074    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:51:26.824624    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:51:38.743165    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:51:50.605572    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:52:02.528317    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:52:14.841783    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:52:26.813441    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:52:38.689862    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:52:50.571612    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:53:02.664663    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:53:14.572115    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:53:26.696581    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:53:38.530735    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:53:50.438073    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:54:02.319649    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:54:14.300643    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:54:26.091721    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:54:38.050266    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:54:49.913162    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:55:02.263169    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:55:14.209803    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:55:26.173559    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:55:38.146741    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:55:50.020822    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:56:01.949923    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:56:13.828808    4937 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 9 lines ...
Machine	i-07f61f5645777d4e5				machine "i-07f61f5645777d4e5" has not yet joined cluster
Node	ip-172-20-43-101.eu-central-1.compute.internal	node "ip-172-20-43-101.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-frr5w			system-node-critical pod "cilium-frr5w" is pending
Pod	kube-system/coredns-5dc785954d-tblb2		system-cluster-critical pod "coredns-5dc785954d-tblb2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-22nlv	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-22nlv" is pending

Validation Failed
W1008 21:56:25.733025    4937 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1008 21:56:35.737641    4877 dumplogs.go:40] /logs/artifacts/30022cec-2880-11ec-b6b4-7efeba256487/kops toolbox dump --name e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1008 21:56:35.752587    4947 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1008 21:56:35.752670    4947 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/08 21:56:45 Dumping node ip-172-20-43-101.eu-central-1.compute.internal
2021/10/08 21:56:50 dumping node not registered in kubernetes: 3.120.192.63
2021/10/08 21:56:50 Dumping node 3.120.192.63
... skipping 1299 lines ...
route-table:rtb-05459ea5862fbcacf	ok
vpc:vpc-0eef455d0fdd3116e	ok
dhcp-options:dopt-0a5eefab8121f67e0	ok
Deleted kubectl config for e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io

Deleted cluster: "e2e-28dea9c821-8ebdc.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace