This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-12 04:44
Elapsed19m50s
Revisionmaster

Test Failures


kubetest2 Up 15m53s

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 159 lines ...
I0712 04:45:43.008952    5901 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0712 04:45:43.010462    5901 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-65-gcd0c4bed67/linux/amd64/kops
I0712 04:45:43.545235    5901 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519
I0712 04:45:43.556722    5901 up.go:44] Cleaning up any leaked resources from previous cluster
I0712 04:45:43.556808    5901 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops toolbox dump --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0712 04:45:43.556864    5901 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops toolbox dump --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
W0712 04:45:44.096937    5901 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0712 04:45:44.097001    5901 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops delete cluster --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --yes
I0712 04:45:44.097014    5901 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops delete cluster --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --yes
I0712 04:45:44.120323    5935 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io" not found
I0712 04:45:44.614806    5901 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/12 04:45:44 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
I0712 04:45:44.623258    5901 http.go:37] curl https://ip.jsb.workers.dev
I0712 04:45:44.709832    5901 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops create cluster --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.11 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20220606.1-x86_64-gp2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.72.53.191/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0712 04:45:44.709876    5901 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops create cluster --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.11 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20220606.1-x86_64-gp2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.72.53.191/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0712 04:45:44.732737    5945 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0712 04:45:44.759839    5945 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0712 04:45:45.289215    5945 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 535 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 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
W0712 04:46:32.866366    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:46:42.905964    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:46:52.946721    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:47:02.986357    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:47:13.028636    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:47:23.064180    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:47:33.109939    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:47:43.147872    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:47:53.195684    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:48:03.228433    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:48:13.267997    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:48:23.300099    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:48:33.332245    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:48:43.379552    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:48:53.415572    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:49:03.451232    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:49:13.484291    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:49:23.523564    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0712 04:49:33.562635    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 15 lines ...
Pod	kube-system/coredns-5fcc7b6498-wwzjp			system-cluster-critical pod "coredns-5fcc7b6498-wwzjp" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-55f2n		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-55f2n" is pending
Pod	kube-system/ebs-csi-controller-54f5cddd4f-q478p		system-cluster-critical pod "ebs-csi-controller-54f5cddd4f-q478p" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:49:47.000162    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 18 lines ...
Pod	kube-system/coredns-autoscaler-6bdc79bb85-55f2n		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-55f2n" is pending
Pod	kube-system/ebs-csi-controller-54f5cddd4f-q478p		system-cluster-critical pod "ebs-csi-controller-54f5cddd4f-q478p" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:49:59.415115    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:50:11.831960    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:50:24.268264    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:50:36.668818    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 25 lines ...
Pod	kube-system/ebs-csi-node-g89dk						system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg						system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9						system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5						system-node-critical pod "ebs-csi-node-mm2d5" is pending
Pod	kube-system/kube-proxy-ip-172-20-38-2.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-38-2.sa-east-1.compute.internal" is pending

Validation Failed
W0712 04:50:49.092675    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:51:01.512758    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:51:14.107525    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:51:26.546581    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:51:38.920474    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:51:51.380188    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:52:03.834212    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:52:16.220894    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:52:28.664914    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:52:41.080269    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:52:53.492496    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:53:06.087557    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:53:18.606793    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:53:31.034457    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:53:43.917643    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:53:56.310673    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:54:08.765585    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:54:21.174624    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:54:33.646228    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:54:46.030391    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:54:58.524213    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:55:11.216745    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:55:23.836181    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:55:36.413738    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:55:48.847412    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:56:01.201550    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:56:13.580888    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:56:26.036454    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:56:38.460457    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:56:51.000695    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:57:03.670019    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:57:16.148522    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:57:28.551456    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:57:41.446995    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:57:53.880808    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:58:06.257137    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:58:18.834541    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:58:31.324820    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:58:43.809424    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:58:56.202650    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:59:08.962571    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:59:21.448386    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:59:33.984624    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:59:46.487115    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 04:59:58.974762    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:00:11.334873    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:00:23.776553    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:00:36.247476    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:00:48.652399    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:01:01.125013    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:01:13.480805    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-f2nzp				system-node-critical pod "ebs-csi-node-f2nzp" is pending
Pod	kube-system/ebs-csi-node-g89dk				system-node-critical pod "ebs-csi-node-g89dk" is pending
Pod	kube-system/ebs-csi-node-gbtxg				system-node-critical pod "ebs-csi-node-gbtxg" is pending
Pod	kube-system/ebs-csi-node-h69c9				system-node-critical pod "ebs-csi-node-h69c9" is pending
Pod	kube-system/ebs-csi-node-mm2d5				system-node-critical pod "ebs-csi-node-mm2d5" is pending

Validation Failed
W0712 05:01:26.088689    5985 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0712 05:01:36.100923    5901 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops toolbox dump --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0712 05:01:36.101121    5901 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops toolbox dump --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0712 05:02:26.579346    5901 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops get cluster --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0712 05:02:26.579441    5901 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops get cluster --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0712 05:02:27.115197    5901 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops get instancegroups --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0712 05:02:27.115231    5901 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/42c3da03-019d-11ed-a50b-a6ae044f977a/kops get instancegroups --name e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 257 lines ...
route-table:rtb-04dfca7bf121168aa	ok
vpc:vpc-03ab16e09e73920ff	ok
dhcp-options:dopt-06f6a2ca0f786e6a5	ok
Deleted kubectl config for e2e-e2e-kops-grid-calico-amzn2-k22-containerd.test-cncf-aws.k8s.io

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