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

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0912 09:25:06.420188    4071 up.go:43] Cleaning up any leaked resources from previous cluster
I0912 09:25:06.420363    4071 dumplogs.go:38] /logs/artifacts/215a89d1-13ab-11ec-a039-aeaa48941d38/kops toolbox dump --name e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0912 09:25:06.441935    4093 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0912 09:25:06.443030    4093 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io" not found
W0912 09:25:06.964137    4071 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0912 09:25:06.964181    4071 down.go:48] /logs/artifacts/215a89d1-13ab-11ec-a039-aeaa48941d38/kops delete cluster --name e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io --yes
I0912 09:25:06.986017    4104 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0912 09:25:06.986133    4104 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io" not found
I0912 09:25:07.526584    4071 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/12 09:25:07 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0912 09:25:07.533680    4071 http.go:37] curl https://ip.jsb.workers.dev
I0912 09:25:07.613771    4071 up.go:144] /logs/artifacts/215a89d1-13ab-11ec-a039-aeaa48941d38/kops create cluster --name e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.4 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.123.127.27/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large
I0912 09:25:07.630185    4114 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0912 09:25:07.630314    4114 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0912 09:25:07.677427    4114 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0912 09:25:08.178195    4114 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I0912 09:25:34.586975    4071 up.go:181] /logs/artifacts/215a89d1-13ab-11ec-a039-aeaa48941d38/kops validate cluster --name e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0912 09:25:34.601546    4135 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0912 09:25:34.601629    4135 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io

W0912 09:25:35.887741    4135 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0912 09:25:45.918980    4135 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-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
W0912 09:25:55.946953    4135 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
W0912 09:26:05.975280    4135 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
W0912 09:26:16.011802    4135 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
W0912 09:26:26.039539    4135 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
W0912 09:26:36.080074    4135 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
W0912 09:26:46.166916    4135 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
W0912 09:26:56.204114    4135 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
W0912 09:27:06.233770    4135 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
W0912 09:27:16.263003    4135 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
W0912 09:27:26.349102    4135 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
W0912 09:27:36.383974    4135 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
W0912 09:27:46.509269    4135 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
W0912 09:27:56.539936    4135 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
W0912 09:28:06.572641    4135 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
W0912 09:28:16.634348    4135 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
W0912 09:28:26.669044    4135 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
W0912 09:28:36.713516    4135 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
W0912 09:28:46.744487    4135 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
W0912 09:28:56.788392    4135 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
W0912 09:29:06.824030    4135 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
W0912 09:29:16.894842    4135 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
W0912 09:29:26.926667    4135 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
W0912 09:29:36.973513    4135 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
W0912 09:29:47.003989    4135 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
W0912 09:29:57.049607    4135 validate_cluster.go:221] (will retry): cluster not yet healthy
W0912 09:30:07.071596    4135 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-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
W0912 09:30:17.153541    4135 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
W0912 09:30:27.193477    4135 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
W0912 09:30:37.240084    4135 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
W0912 09:30:47.269358    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:31:00.288105    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:31:12.386295    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:31:25.383069    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:31:37.424087    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:31:49.267634    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:32:01.233004    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:32:13.163893    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:32:25.126262    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:32:37.225585    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:32:49.223911    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:33:01.106723    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:33:13.202221    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:33:25.196843    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:33:37.212738    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:33:49.130131    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:34:01.046198    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:34:12.986455    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:34:24.872960    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:34:36.813108    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:34:48.758663    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:35:01.183331    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:35:13.135234    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:35:25.051250    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:35:37.016300    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:35:48.857962    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:36:00.777834    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:36:12.716943    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:36:24.694592    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:36:36.582853    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:36:48.427273    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:37:00.339769    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:37:12.366100    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:37:24.260392    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:37:36.154160    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:37:48.132002    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:37:59.982169    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:38:11.839902    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:38:23.713133    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:38:35.549316    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:38:47.708947    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:38:59.983092    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:39:12.011744    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:39:24.005020    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:39:35.954906    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:39:47.914560    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:40:00.008803    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:40:12.025310    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:40:23.931305    4135 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-0b4e5a0a02e05d014				machine "i-0b4e5a0a02e05d014" has not yet joined cluster
Node	ip-172-20-41-205.eu-central-1.compute.internal	node "ip-172-20-41-205.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-xctwc			system-node-critical pod "cilium-xctwc" is pending
Pod	kube-system/coredns-5dc785954d-9g6pb		system-cluster-critical pod "coredns-5dc785954d-9g6pb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-cssrj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-cssrj" is pending

Validation Failed
W0912 09:40:35.911974    4135 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0912 09:40:45.920565    4071 dumplogs.go:38] /logs/artifacts/215a89d1-13ab-11ec-a039-aeaa48941d38/kops toolbox dump --name e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0912 09:40:45.940188    4145 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0912 09:40:45.940402    4145 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/12 09:40:55 Dumping node ip-172-20-41-205.eu-central-1.compute.internal
2021/09/12 09:41:01 dumping node not registered in kubernetes: 3.122.253.118
2021/09/12 09:41:01 Dumping node 3.122.253.118
... skipping 1165 lines ...
route-table:rtb-035085f1b8fae390d	ok
vpc:vpc-0feb4e23807b9cc8b	ok
dhcp-options:dopt-06faf4672a5be7371	ok
Deleted kubectl config for e2e-d6612ce0e4-53349.test-cncf-aws.k8s.io

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