This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-06-04 18:17
Elapsed25m35s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 156 lines ...
I0604 18:17:58.884646    5686 common.go:152] Using cluster name: 
I0604 18:17:58.884693    5686 http.go:37] curl https://storage.googleapis.com/kubernetes-release/release/stable-1.22.txt
I0604 18:17:58.941543    5686 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0604 18:17:58.943243    5686 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.24.0-beta.2+v1.24.0-beta.1-2-g993a3b42ea/linux/amd64/kops
I0604 18:17:59.516350    5686 up.go:44] Cleaning up any leaked resources from previous cluster
I0604 18:17:59.516439    5686 dumplogs.go:45] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops toolbox dump --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core
W0604 18:18:00.010944    5686 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0604 18:18:00.010993    5686 down.go:48] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops delete cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --yes
I0604 18:18:00.029753    5714 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0604 18:18:00.029871    5714 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io" not found
I0604 18:18:00.495606    5686 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/06/04 18:18:00 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0604 18:18:00.505789    5686 http.go:37] curl https://ip.jsb.workers.dev
I0604 18:18:00.599565    5686 up.go:156] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops create cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.10 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=075585003325/Flatcar-stable-3139.2.1-hvm --channel=alpha --networking=calico --container-runtime=docker --admin-access 35.193.93.145/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-west-3a --master-size c5.large
I0604 18:18:00.618980    5724 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0604 18:18:00.619164    5724 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
I0604 18:18:00.643661    5724 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0604 18:18:01.110197    5724 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 531 lines ...

I0604 18:18:38.157798    5686 up.go:240] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops validate cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 20m0s
I0604 18:18:38.176837    5779 featureflag.go:164] FeatureFlag "SpecOverrideFlag"=true
I0604 18:18:38.176915    5779 featureflag.go:164] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io

W0604 18:18:39.317382    5779 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:18:49.352841    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:18:59.387386    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:19:09.424741    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:19:19.460831    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:19:29.495205    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:19:39.531038    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:19:49.575395    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:19:59.605207    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:20:09.642233    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:20:19.680255    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:20:29.709618    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:20:39.737967    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:20:49.768760    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:20:59.805403    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:21:09.852958    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:21:19.889004    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:21:29.933564    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:21:39.969491    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

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
W0604 18:21:50.006298    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-j46wc						system-cluster-critical pod "coredns-5b7f7db4db-j46wc" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd					system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is pending
Pod	kube-system/ebs-csi-controller-f58d95bd5-7l52h					system-cluster-critical pod "ebs-csi-controller-f58d95bd5-7l52h" is pending
Pod	kube-system/ebs-csi-node-47s5v							system-node-critical pod "ebs-csi-node-47s5v" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-63-195.eu-west-3.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-63-195.eu-west-3.compute.internal" is pending

Validation Failed
W0604 18:22:02.901809    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...
Machine	i-0577b5abeec8771bc				machine "i-0577b5abeec8771bc" has not yet joined cluster
Machine	i-081032a3bf3ca4c51				machine "i-081032a3bf3ca4c51" has not yet joined cluster
Machine	i-0b329586d834cb4a2				machine "i-0b329586d834cb4a2" has not yet joined cluster
Pod	kube-system/coredns-5b7f7db4db-j46wc		system-cluster-critical pod "coredns-5b7f7db4db-j46wc" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is pending

Validation Failed
W0604 18:22:14.917953    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 17 lines ...
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is pending
Pod	kube-system/ebs-csi-node-5xt7j			system-node-critical pod "ebs-csi-node-5xt7j" is pending
Pod	kube-system/ebs-csi-node-hstwd			system-node-critical pod "ebs-csi-node-hstwd" is pending
Pod	kube-system/ebs-csi-node-mqpfq			system-node-critical pod "ebs-csi-node-mqpfq" is pending
Pod	kube-system/ebs-csi-node-x4fbw			system-node-critical pod "ebs-csi-node-x4fbw" is pending

Validation Failed
W0604 18:22:26.813998    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 17 lines ...
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is pending
Pod	kube-system/ebs-csi-node-5xt7j			system-node-critical pod "ebs-csi-node-5xt7j" is pending
Pod	kube-system/ebs-csi-node-hstwd			system-node-critical pod "ebs-csi-node-hstwd" is pending
Pod	kube-system/ebs-csi-node-mqpfq			system-node-critical pod "ebs-csi-node-mqpfq" is pending
Pod	kube-system/ebs-csi-node-x4fbw			system-node-critical pod "ebs-csi-node-x4fbw" is pending

Validation Failed
W0604 18:22:38.810775    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 13 lines ...
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is pending
Pod	kube-system/ebs-csi-node-5xt7j			system-node-critical pod "ebs-csi-node-5xt7j" is pending
Pod	kube-system/ebs-csi-node-hstwd			system-node-critical pod "ebs-csi-node-hstwd" is pending
Pod	kube-system/ebs-csi-node-mqpfq			system-node-critical pod "ebs-csi-node-mqpfq" is pending
Pod	kube-system/ebs-csi-node-x4fbw			system-node-critical pod "ebs-csi-node-x4fbw" is pending

Validation Failed
W0604 18:22:50.748157    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Pod	kube-system/calico-node-5h2mw						system-node-critical pod "calico-node-5h2mw" is not ready (calico-node)
Pod	kube-system/calico-node-7lllz						system-node-critical pod "calico-node-7lllz" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-hstwd						system-node-critical pod "ebs-csi-node-hstwd" is pending
Pod	kube-system/ebs-csi-node-x4fbw						system-node-critical pod "ebs-csi-node-x4fbw" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-52.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-52.eu-west-3.compute.internal" is pending

Validation Failed
W0604 18:23:03.093158    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Node	ip-172-20-57-221.eu-west-3.compute.internal				node "ip-172-20-57-221.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/kube-proxy-ip-172-20-54-33.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-33.eu-west-3.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-221.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-221.eu-west-3.compute.internal" is pending

Validation Failed
W0604 18:23:15.004331    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-57-221.eu-west-3.compute.internal	node "ip-172-20-57-221.eu-west-3.compute.internal" of role "node" is not ready

Validation Failed
W0604 18:23:26.862362    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-57-221.eu-west-3.compute.internal	node "ip-172-20-57-221.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-lc75z			system-node-critical pod "calico-node-lc75z" is pending

Validation Failed
W0604 18:23:38.847175    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-57-221.eu-west-3.compute.internal	node "ip-172-20-57-221.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-lc75z			system-node-critical pod "calico-node-lc75z" is pending

Validation Failed
W0604 18:23:50.858092    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-lc75z	system-node-critical pod "calico-node-lc75z" is pending

Validation Failed
W0604 18:24:02.818518    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-lc75z	system-node-critical pod "calico-node-lc75z" is pending

Validation Failed
W0604 18:24:14.784316    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME				MESSAGE
Pod	kube-system/calico-node-lc75z	system-node-critical pod "calico-node-lc75z" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-x4fbw	system-node-critical pod "ebs-csi-node-x4fbw" is not ready (ebs-plugin,liveness-probe,node-driver-registrar)

Validation Failed
W0604 18:24:26.830840    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 96 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-46-52.eu-west-3.compute.internal	node "ip-172-20-46-52.eu-west-3.compute.internal" of role "node" is not ready

Validation Failed
W0604 18:25:50.680327    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-46-52.eu-west-3.compute.internal	node "ip-172-20-46-52.eu-west-3.compute.internal" of role "node" is not ready

Validation Failed
W0604 18:26:02.976171    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Node	ip-172-20-46-52.eu-west-3.compute.internal				node "ip-172-20-46-52.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-5lt6f						system-node-critical pod "calico-node-5lt6f" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd				system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-g9b4z						system-node-critical pod "ebs-csi-node-g9b4z" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-52.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-52.eu-west-3.compute.internal" is not ready (kube-proxy)

Validation Failed
W0604 18:26:14.962273    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Node	ip-172-20-46-52.eu-west-3.compute.internal				node "ip-172-20-46-52.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-5lt6f						system-node-critical pod "calico-node-5lt6f" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd				system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-g9b4z						system-node-critical pod "ebs-csi-node-g9b4z" is pending
Pod	kube-system/kube-proxy-ip-172-20-46-52.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-46-52.eu-west-3.compute.internal" is not ready (kube-proxy)

Validation Failed
W0604 18:26:26.959164    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 11 lines ...
Node	ip-172-20-61-19.eu-west-3.compute.internal	node "ip-172-20-61-19.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-5lt6f			system-node-critical pod "calico-node-5lt6f" is not ready (calico-node)
Pod	kube-system/coredns-5b7f7db4db-j46wc		system-cluster-critical pod "coredns-5b7f7db4db-j46wc" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-g9b4z			system-node-critical pod "ebs-csi-node-g9b4z" is pending

Validation Failed
W0604 18:26:38.826217    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Node	ip-172-20-61-19.eu-west-3.compute.internal				node "ip-172-20-61-19.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5b7f7db4db-j46wc					system-cluster-critical pod "coredns-5b7f7db4db-j46wc" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd				system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-g9b4z						system-node-critical pod "ebs-csi-node-g9b4z" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-19.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-19.eu-west-3.compute.internal" is not ready (kube-proxy)

Validation Failed
W0604 18:26:50.960620    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 11 lines ...
Pod	kube-system/calico-node-8qhvh						system-node-critical pod "calico-node-8qhvh" is pending
Pod	kube-system/coredns-5b7f7db4db-j46wc					system-cluster-critical pod "coredns-5b7f7db4db-j46wc" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd				system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-x9ldq						system-node-critical pod "ebs-csi-node-x9ldq" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-19.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-19.eu-west-3.compute.internal" is not ready (kube-proxy)

Validation Failed
W0604 18:27:02.984382    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/calico-node-8qhvh			system-node-critical pod "calico-node-8qhvh" is pending
Pod	kube-system/coredns-5b7f7db4db-ktbrv		system-cluster-critical pod "coredns-5b7f7db4db-ktbrv" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-x9ldq			system-node-critical pod "ebs-csi-node-x9ldq" is pending

Validation Failed
W0604 18:27:15.154267    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-ktbrv		system-cluster-critical pod "coredns-5b7f7db4db-ktbrv" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-x9ldq			system-node-critical pod "ebs-csi-node-x9ldq" is pending

Validation Failed
W0604 18:27:27.154675    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:27:39.098413    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:27:50.972056    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-54-33.eu-west-3.compute.internal	node "ip-172-20-54-33.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:28:02.986122    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-54-33.eu-west-3.compute.internal	node "ip-172-20-54-33.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:28:14.922437    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
KIND	NAME									MESSAGE
Node	ip-172-20-54-33.eu-west-3.compute.internal				node "ip-172-20-54-33.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-wrqz8						system-node-critical pod "calico-node-wrqz8" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd				system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/kube-proxy-ip-172-20-54-33.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-33.eu-west-3.compute.internal" is not ready (kube-proxy)

Validation Failed
W0604 18:28:26.855243    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
KIND	NAME									MESSAGE
Node	ip-172-20-54-33.eu-west-3.compute.internal				node "ip-172-20-54-33.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-wrqz8						system-node-critical pod "calico-node-wrqz8" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd				system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/kube-proxy-ip-172-20-54-33.eu-west-3.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-33.eu-west-3.compute.internal" is not ready (kube-proxy)

Validation Failed
W0604 18:28:38.886040    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Node	ip-172-20-54-33.eu-west-3.compute.internal	node "ip-172-20-54-33.eu-west-3.compute.internal" of role "node" is not ready
Pod	kube-system/calico-node-wrqz8			system-node-critical pod "calico-node-wrqz8" is not ready (calico-node)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-node-5xt7j			system-node-critical pod "ebs-csi-node-5xt7j" is not ready (ebs-plugin,liveness-probe,node-driver-registrar)

Validation Failed
W0604 18:28:50.781410    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:29:02.882147    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:29:14.867037    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:29:26.761673    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:29:38.692124    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:29:50.574936    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:30:02.996548    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:30:14.922142    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:30:26.820510    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:30:38.783313    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:30:50.653681    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:31:02.596566    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:31:14.518740    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:31:26.409838    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:31:38.462432    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Node	ip-172-20-63-195.eu-west-3.compute.internal	node "ip-172-20-63-195.eu-west-3.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:31:50.423425    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
W0604 18:32:00.572153    5779 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.38.45.196:443: connect: connection refused
W0604 18:32:10.722358    5779 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.38.45.196:443: connect: connection refused
W0604 18:32:27.974013    5779 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.38.45.196:443: connect: connection refused
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

NODE STATUS
... skipping 9 lines ...
Pod	kube-system/calico-node-6t94n			system-node-critical pod "calico-node-6t94n" is not ready (calico-node)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/dns-controller-f7ff8fbd5-vghm5	system-cluster-critical pod "dns-controller-f7ff8fbd5-vghm5" is not ready (dns-controller)
Pod	kube-system/ebs-csi-node-47s5v			system-node-critical pod "ebs-csi-node-47s5v" is not ready (ebs-plugin,liveness-probe,node-driver-registrar)
Pod	kube-system/kops-controller-hfmrt		system-cluster-critical pod "kops-controller-hfmrt" is not ready (kops-controller)

Validation Failed
W0604 18:32:40.800582    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 10 lines ...
Pod	kube-system/calico-kube-controllers-849f76867f-6r5wk	system-cluster-critical pod "calico-kube-controllers-849f76867f-6r5wk" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-6t94n				system-node-critical pod "calico-node-6t94n" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd		system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)
Pod	kube-system/ebs-csi-controller-f58d95bd5-7l52h		system-cluster-critical pod "ebs-csi-controller-f58d95bd5-7l52h" is not ready (csi-attacher,csi-provisioner,csi-resizer,ebs-plugin,liveness-probe)
Pod	kube-system/ebs-csi-node-47s5v				system-node-critical pod "ebs-csi-node-47s5v" is not ready (ebs-plugin,liveness-probe,node-driver-registrar)

Validation Failed
W0604 18:32:52.687507    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/calico-node-6t94n			system-node-critical pod "calico-node-6t94n" is not ready (calico-node)
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:33:04.663348    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:33:16.671713    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:33:28.608458    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:33:40.644620    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:33:52.887148    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:34:04.882557    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:34:16.741127    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:34:28.615941    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:34:40.520882    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:34:52.437229    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:35:04.531042    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:35:16.516115    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:35:28.453706    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:35:40.455669    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:35:52.352051    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:36:04.338571    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:36:16.186027    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:36:28.067133    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:36:39.978661    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:36:51.972026    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:37:04.001955    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:37:16.001130    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:37:28.005949    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:37:39.979261    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:37:52.310597    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:38:04.365165    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:38:16.379018    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:38:28.314455    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-3a	Master	c5.large	1	1	eu-west-3a
nodes-eu-west-3a	Node	t3.medium	4	4	eu-west-3a

... skipping 6 lines ...
ip-172-20-63-195.eu-west-3.compute.internal	master	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-autoscaler-6fccfff6b-vftpd	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-vftpd" is not ready (autoscaler)

Validation Failed
W0604 18:38:40.175953    5779 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0604 18:38:50.179946    5686 dumplogs.go:45] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops toolbox dump --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user core
I0604 18:39:27.103234    5686 dumplogs.go:78] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops get cluster --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io -o yaml
I0604 18:39:27.625802    5686 dumplogs.go:78] /logs/artifacts/741dedf2-e432-11ec-b35f-e6755cd0a106/kops get instancegroups --name e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io -o yaml
I0604 18:39:28.383770    5686 dumplogs.go:97] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info
I0604 18:39:39.301758    5686 dumplogs.go:126] kubectl --request-timeout 5s get csinodes --all-namespaces -o yaml
I0604 18:39:40.213151    5686 dumplogs.go:126] kubectl --request-timeout 5s get csidrivers --all-namespaces -o yaml
... skipping 306 lines ...
route-table:rtb-0c36707c1974a6bca	ok
vpc:vpc-0447ba8500355f627	ok
dhcp-options:dopt-08dd194b121e21546	ok
Deleted kubectl config for e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-calico-flatcar-k22-docker.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace