This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2023-03-23 04:19
Elapsed19m51s
Revisionmaster

Test Failures


kubetest2 Up 15m56s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 139 lines ...
I0323 04:20:11.428016    6181 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0323 04:20:11.455273    6181 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-490-g1459d54fa9/linux/amd64/kops
I0323 04:20:12.243688    6181 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519
I0323 04:20:12.252025    6181 up.go:44] Cleaning up any leaked resources from previous cluster
I0323 04:20:12.252138    6181 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops toolbox dump --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0323 04:20:12.252161    6181 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops toolbox dump --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
Error: Cluster.kops.k8s.io "e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io" not found
W0323 04:20:12.748409    6181 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0323 04:20:12.748463    6181 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops delete cluster --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --yes
I0323 04:20:12.748520    6181 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops delete cluster --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --yes
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io" not found
I0323 04:20:13.276482    6181 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2023/03/23 04:20:13 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
I0323 04:20:13.286295    6181 http.go:37] curl https://ip.jsb.workers.dev
I0323 04:20:13.371010    6181 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops create cluster --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.27.0-beta.0.66+d2be69ac11346d --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20230303 --channel=alpha --networking=calico --node-size=c5.large --master-size=c5.large --discovery-store=s3://k8s-kops-prow/discovery --admin-access 34.72.233.135/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1c
I0323 04:20:13.371065    6181 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops create cluster --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.27.0-beta.0.66+d2be69ac11346d --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20230303 --channel=alpha --networking=calico --node-size=c5.large --master-size=c5.large --discovery-store=s3://k8s-kops-prow/discovery --admin-access 34.72.233.135/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1c
I0323 04:20:13.418453    6222 create_cluster.go:882] Using SSH public key: /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519.pub
I0323 04:20:13.878202    6222 new_cluster.go:1347] Cloud Provider ID: "aws"
I0323 04:20:14.392029    6222 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet eu-central-1c
... skipping 529 lines ...
I0323 04:20:26.248898    6243 keypair.go:226] Issuing new certificate: "etcd-peers-ca-events"
W0323 04:20:26.306521    6243 vfs_keystorereader.go:143] CA private key was not found
I0323 04:20:26.361724    6243 keypair.go:226] Issuing new certificate: "kubernetes-ca"
I0323 04:20:26.364203    6243 keypair.go:226] Issuing new certificate: "service-account"
I0323 04:20:27.922984    6243 executor.go:111] Tasks: 51 done / 102 total; 23 can run
I0323 04:20:29.844722    6243 executor.go:111] Tasks: 74 done / 102 total; 24 can run
W0323 04:20:31.879465    6243 retry_handler.go:99] Got RequestLimitExceeded error on AWS request (ec2::AuthorizeSecurityGroupIngress)
I0323 04:20:33.163665    6243 executor.go:111] Tasks: 98 done / 102 total; 2 can run
I0323 04:20:34.638839    6243 executor.go:155] No progress made, sleeping before retrying 2 task(s)
I0323 04:20:44.639088    6243 executor.go:111] Tasks: 98 done / 102 total; 2 can run
I0323 04:20:46.422219    6243 executor.go:111] Tasks: 100 done / 102 total; 2 can run
I0323 04:20:46.626777    6243 executor.go:111] Tasks: 102 done / 102 total; 0 can run
I0323 04:20:49.681624    6243 dns.go:232] Pre-creating DNS records
... skipping 20 lines ...

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 control plane node 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
W0323 04:21:01.670626    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:21:11.701290    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:21:21.744680    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:21:31.776345    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:21:41.806140    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:21:51.863406    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:22:01.895205    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:22:11.926025    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:22:21.961892    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:22:31.994126    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:22:42.024828    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:22:52.057041    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:23:02.102419    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:23:12.134826    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:23:22.179529    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:23:32.226805    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:23:42.260021    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:23:52.294239    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:24:02.326707    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:24:12.357594    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:24:22.420140    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:24:32.482191    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:24:42.510792    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:24:52.541640    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:25:02.587764    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:25:12.620129    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:25:22.650455    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:25:32.679034    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

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 control plane node 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
W0323 04:25:42.710101    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:25:55.522968    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:26:07.458150    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:26:19.417688    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:26:31.355596    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:26:43.277337    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:26:55.351062    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:27:07.408547    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:27:19.378092    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:27:31.387384    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:27:44.373846    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:27:56.337401    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:28:08.395197    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:28:20.334401    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:28:32.464654    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:28:44.357572    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:28:56.236942    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:29:08.238451    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:29:20.133147    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:29:32.236247    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:29:44.221437    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:29:56.691670    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:30:08.770594    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:30:20.763492    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:30:32.785995    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:30:44.741710    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:30:56.771280    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:31:08.904101    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:31:21.024989    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:31:33.034104    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:31:45.059479    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:31:57.141745    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:32:09.056106    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:32:21.214289    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:32:33.246332    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:32:45.245321    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:32:57.281903    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:33:09.287335    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:33:21.256597    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:33:34.129962    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:33:46.453065    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:33:58.461486    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:34:10.449134    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:34:22.425601    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:34:34.450505    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:34:46.389602    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:34:58.283677    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:35:10.282950    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:35:22.220230    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:35:34.178616    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:35:46.135116    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-eu-central-1c	ControlPlane	c5.large	1	1	eu-central-1c
nodes-eu-central-1c		Node		c5.large	4	4	eu-central-1c

... skipping 9 lines ...
Machine	i-0ee982b3b3642162f				machine "i-0ee982b3b3642162f" has not yet joined cluster
Pod	kube-system/coredns-745bddcfbb-l4s2j		system-cluster-critical pod "coredns-745bddcfbb-l4s2j" is pending
Pod	kube-system/coredns-autoscaler-8495f5575-krb29	system-cluster-critical pod "coredns-autoscaler-8495f5575-krb29" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-rmwng	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-rmwng" is pending
Pod	kube-system/ebs-csi-controller-748b7fbccd-t5qdm	system-cluster-critical pod "ebs-csi-controller-748b7fbccd-t5qdm" is pending

Validation Failed
W0323 04:35:58.165275    6264 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: validation failed: wait time exceeded during validation
I0323 04:36:08.179877    6181 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops toolbox dump --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0323 04:36:08.179963    6181 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/bcdbbc05-c931-11ed-8be2-1221e2764aa1/kops toolbox dump --name e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
2023/03/23 04:36:29 Dumping node i-0d21e5449fb8f559f
2023/03/23 04:36:37 dumping node not registered in kubernetes: 3.68.27.137
2023/03/23 04:36:37 Dumping node 3.68.27.137
2023/03/23 04:36:42 dumping node not registered in kubernetes: 3.71.70.191
... skipping 272 lines ...
route-table:rtb-0de36d6e25339063c	ok
vpc:vpc-0f5a2a0409ffe927d	ok
dhcp-options:dopt-01796b8dabb0c7a69	ok
Deleted kubectl config for e2e-e2e-kops-aws-amd64-conformance.test-cncf-aws.k8s.io

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