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

No Test Failures!


Error lines from build-log.txt

... skipping 130 lines ...
I1009 20:04:08.358560    4749 up.go:43] Cleaning up any leaked resources from previous cluster
I1009 20:04:08.358609    4749 dumplogs.go:40] /logs/artifacts/d3d793fb-293b-11ec-b781-c649eef4635a/kops toolbox dump --name e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1009 20:04:08.374433    4770 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1009 20:04:08.374547    4770 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io" not found
W1009 20:04:08.904615    4749 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1009 20:04:08.904698    4749 down.go:48] /logs/artifacts/d3d793fb-293b-11ec-b781-c649eef4635a/kops delete cluster --name e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io --yes
I1009 20:04:08.919791    4780 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1009 20:04:08.919903    4780 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io" not found
I1009 20:04:09.406778    4749 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/09 20:04:09 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
I1009 20:04:09.416208    4749 http.go:37] curl https://ip.jsb.workers.dev
I1009 20:04:09.499746    4749 up.go:144] /logs/artifacts/d3d793fb-293b-11ec-b781-c649eef4635a/kops create cluster --name e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20211001.1-x86_64-gp2 --channel=alpha --networking=cilium-etcd --container-runtime=containerd --admin-access 34.121.71.138/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large
I1009 20:04:09.521303    4790 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1009 20:04:09.521668    4790 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1009 20:04:09.574696    4790 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1009 20:04:10.214329    4790 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1009 20:04:36.329041    4749 up.go:181] /logs/artifacts/d3d793fb-293b-11ec-b781-c649eef4635a/kops validate cluster --name e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1009 20:04:36.355606    4810 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1009 20:04:36.355743    4810 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io

W1009 20:04:37.694521    4810 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-25ccd870e8-e7a62.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
W1009 20:04:47.731429    4810 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
W1009 20:04:57.762230    4810 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
W1009 20:05:07.800521    4810 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
W1009 20:05:17.849987    4810 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
W1009 20:05:27.892806    4810 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
W1009 20:05:37.931588    4810 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
W1009 20:05:47.984353    4810 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
W1009 20:05:58.021965    4810 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
W1009 20:06:08.056791    4810 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
W1009 20:06:18.100849    4810 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
W1009 20:06:28.145114    4810 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
W1009 20:06:38.183627    4810 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
W1009 20:06:48.230227    4810 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
W1009 20:06:58.260647    4810 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
W1009 20:07:08.300615    4810 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
W1009 20:07:18.343945    4810 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
W1009 20:07:28.379656    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
W1009 20:07:38.413401    4810 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-25ccd870e8-e7a62.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
W1009 20:07:48.444545    4810 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
W1009 20:07:58.478921    4810 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
W1009 20:08:08.524716    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:08:21.641089    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:08:33.713696    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:08:45.576500    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:08:57.526658    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:09:09.347439    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:09:21.287987    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:09:33.338900    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:09:45.244659    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:09:57.243371    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:10:09.287397    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:10:21.268110    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:10:33.256014    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:10:45.245133    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:10:57.201714    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:11:09.124073    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:11:21.076666    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:11:33.026378    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:11:44.997517    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:11:56.927586    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:12:08.818978    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:12:21.106705    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:12:32.960700    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:12:44.898412    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:12:56.869372    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:13:08.761577    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:13:20.751386    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:13:32.777419    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:13:44.761005    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:13:56.678518    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:14:08.614594    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:14:20.526616    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:14:32.492514    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:14:44.368498    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:14:56.449254    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:15:08.660034    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:15:20.579850    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:15:32.825933    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:15:44.745565    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:15:56.657801    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:16:08.570324    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:16:20.876043    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:16:32.831686    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:16:44.659496    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:16:56.565243    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:17:08.547624    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:17:20.566736    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:17:32.497573    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:17:44.437416    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:17:56.385994    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:18:08.315903    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:18:20.206532    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:18:32.166126    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:18:44.096898    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:18:56.026874    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:19:08.087219    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:19:20.038777    4810 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-0e8e9f3ffe124c463				machine "i-0e8e9f3ffe124c463" has not yet joined cluster
Node	ip-172-20-35-1.eu-central-1.compute.internal	node "ip-172-20-35-1.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gxmln			system-node-critical pod "cilium-gxmln" is pending
Pod	kube-system/coredns-64497985bd-9sj7k		system-cluster-critical pod "coredns-64497985bd-9sj7k" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-c78r6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-c78r6" is pending

Validation Failed
W1009 20:19:31.937601    4810 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1009 20:19:41.943186    4749 dumplogs.go:40] /logs/artifacts/d3d793fb-293b-11ec-b781-c649eef4635a/kops toolbox dump --name e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1009 20:19:41.960227    4822 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1009 20:19:41.960346    4822 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/09 20:19:51 Dumping node ip-172-20-35-1.eu-central-1.compute.internal
2021/10/09 20:19:57 dumping node not registered in kubernetes: 3.120.186.67
2021/10/09 20:19:57 Dumping node 3.120.186.67
... skipping 1209 lines ...
route-table:rtb-08b88cff5ae72c620	ok
vpc:vpc-087f46f80c2d83c22	ok
dhcp-options:dopt-0a335f7e3544c9188	ok
Deleted kubectl config for e2e-25ccd870e8-e7a62.test-cncf-aws.k8s.io

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