This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-09-11 23:40
Elapsed20m53s
Revisionmaster

Test Failures


kubetest2 Up 16m8s

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 166 lines ...
I0911 23:41:49.598322    6080 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0911 23:41:49.600060    6080 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-beta.2+v1.25.0-beta.1-63-g34e086ff4a/linux/amd64/kops
I0911 23:41:50.704399    6080 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519
I0911 23:41:50.712069    6080 up.go:44] Cleaning up any leaked resources from previous cluster
I0911 23:41:50.712192    6080 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0911 23:41:50.712217    6080 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0911 23:41:51.232007    6080 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0911 23:41:51.232061    6080 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --yes
I0911 23:41:51.232074    6080 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --yes
I0911 23:41:51.264666    6114 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io" not found
I0911 23:41:51.717525    6080 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/11 23:41:51 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
I0911 23:41:51.729335    6080 http.go:37] curl https://ip.jsb.workers.dev
I0911 23:41:51.841619    6080 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.13 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220901 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.188.33.172/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0911 23:41:51.841663    6080 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.13 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220901 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.188.33.172/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0911 23:41:51.872304    6125 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0911 23:41:51.888926    6125 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0911 23:41:52.426228    6125 new_cluster.go:1277]  Cloud Provider ID = aws
... skipping 570 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
W0911 23:42:45.736722    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:42:55.785422    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:43:05.833823    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:43:15.886278    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:43:25.920652    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:43:35.953129    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:43:45.988672    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:43:56.026601    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:44:06.059581    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:44:16.092640    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:44:26.126626    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:44:36.164568    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:44:46.199890    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:44:56.238304    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:45:06.280006    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:45:16.312653    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:45:26.351437    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-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
W0911 23:45:36.399411    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 15 lines ...
Pod	kube-system/coredns-autoscaler-6658b4bf85-552wq	system-cluster-critical pod "coredns-autoscaler-6658b4bf85-552wq" is pending
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is pending
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is pending
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is pending
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is pending

Validation Failed
W0911 23:45:49.835252    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-469tl				system-node-critical pod "ebs-csi-node-469tl" is pending
Pod	kube-system/ebs-csi-node-b9mlk				system-node-critical pod "ebs-csi-node-b9mlk" is pending
Pod	kube-system/ebs-csi-node-kln8c				system-node-critical pod "ebs-csi-node-kln8c" is pending
Pod	kube-system/ebs-csi-node-ptfbt				system-node-critical pod "ebs-csi-node-ptfbt" is pending
Pod	kube-system/ebs-csi-node-xxzhk				system-node-critical pod "ebs-csi-node-xxzhk" is pending

Validation Failed
W0911 23:46:02.169292    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 20 lines ...
Pod	kube-system/ebs-csi-node-469tl				system-node-critical pod "ebs-csi-node-469tl" is pending
Pod	kube-system/ebs-csi-node-b9mlk				system-node-critical pod "ebs-csi-node-b9mlk" is pending
Pod	kube-system/ebs-csi-node-kln8c				system-node-critical pod "ebs-csi-node-kln8c" is pending
Pod	kube-system/ebs-csi-node-ptfbt				system-node-critical pod "ebs-csi-node-ptfbt" is pending
Pod	kube-system/ebs-csi-node-xxzhk				system-node-critical pod "ebs-csi-node-xxzhk" is pending

Validation Failed
W0911 23:46:14.471887    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 15 lines ...
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is pending
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is pending
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is pending
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is pending
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is pending

Validation Failed
W0911 23:46:26.927672    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is pending
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is pending
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is pending
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is pending

Validation Failed
W0911 23:46:39.181692    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is pending

Validation Failed
W0911 23:46:51.569735    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:47:03.922000    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:47:16.249197    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:47:28.459635    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:47:40.751164    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:47:53.090822    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:48:05.424941    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)

Validation Failed
W0911 23:48:17.668051    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:48:30.238247    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:48:42.624490    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)

Validation Failed
W0911 23:48:54.934114    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:49:07.289122    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:49:19.603562    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)

Validation Failed
W0911 23:49:32.013830    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)

Validation Failed
W0911 23:49:44.926951    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:49:57.219698    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:50:09.539541    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:50:21.755385    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:50:34.060763    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:50:46.288788    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:50:58.659209    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:51:11.096329    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)

Validation Failed
W0911 23:51:23.273130    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)

Validation Failed
W0911 23:51:35.495799    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)

Validation Failed
W0911 23:51:47.761765    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:52:00.084890    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:52:12.513903    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:52:24.894525    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:52:37.213804    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:52:49.520944    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:53:01.858361    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:53:14.167715    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:53:26.570063    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:53:39.369446    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:53:51.917354    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:54:04.279447    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:54:16.736024    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:54:29.048782    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:54:41.508841    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)

Validation Failed
W0911 23:54:53.889120    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5fcc7b6498-z9t7v		system-cluster-critical pod "coredns-5fcc7b6498-z9t7v" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:55:06.509339    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-7b6b885c79-rsl8x	system-cluster-critical pod "ebs-csi-controller-7b6b885c79-rsl8x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:55:18.826027    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:55:31.143343    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:55:43.553426    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:55:55.860689    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:56:08.175702    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:56:20.613510    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:56:33.189228    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:56:45.539738    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:56:57.818495    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:57:10.297793    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:57:22.589082    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:57:35.477325    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-469tl			system-node-critical pod "ebs-csi-node-469tl" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b9mlk			system-node-critical pod "ebs-csi-node-b9mlk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kln8c			system-node-critical pod "ebs-csi-node-kln8c" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ptfbt			system-node-critical pod "ebs-csi-node-ptfbt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xxzhk			system-node-critical pod "ebs-csi-node-xxzhk" is not ready (ebs-plugin)

Validation Failed
W0911 23:57:47.917571    6166 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0911 23:57:57.923703    6080 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0911 23:57:57.923761    6080 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0911 23:59:00.037428    6080 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io -o yaml
I0911 23:59:00.037488    6080 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io -o yaml
I0911 23:59:00.545674    6080 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io -o yaml
I0911 23:59:00.545714    6080 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/11e73f68-322b-11ed-99df-92296d848f70/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io -o yaml
... skipping 309 lines ...
route-table:rtb-0ec863a4074cb391b	ok
vpc:vpc-058b6f4f36d6aa119	ok
dhcp-options:dopt-0b20992c6c5ddc73b	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-u2204-k22-docker.test-cncf-aws.k8s.io

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