This job view page is being replaced by Spyglass soon. Check out the new job view.
PRReillyBrogan: Add bidirectional BPF mount for Cilium >= 1.9.10 or >= 1.10.4
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-25 05:48
Elapsed24m22s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 531 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0925 05:52:32.477642    4856 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/15040e0f-1dc4-11ec-8af3-22f8e8a1ce5c/kops
I0925 05:52:32.648828    4856 up.go:43] Cleaning up any leaked resources from previous cluster
I0925 05:52:32.648869    4856 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0925 05:52:32.668124   12454 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 05:52:32.668226   12454 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0925 05:52:33.125956    4856 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0925 05:52:33.126038    4856 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --yes
I0925 05:52:33.141828   12465 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 05:52:33.142447   12465 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
I0925 05:52:33.610211    4856 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/25 05:52:33 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
I0925 05:52:33.617159    4856 http.go:37] curl https://ip.jsb.workers.dev
I0925 05:52:33.702912    4856 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.2 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210907 --channel=alpha --networking=weave --container-runtime=containerd --node-size=t3.large --admin-access 35.202.107.7/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0925 05:52:33.718072   12475 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 05:52:33.718301   12475 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0925 05:52:33.738352   12475 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0925 05:52:34.230047   12475 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 32 lines ...

I0925 05:53:04.942601    4856 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0925 05:53:04.984864   12496 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 05:53:04.986048   12496 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0925 05:53:06.467764   12496 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0925 05:53:16.512877   12496 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:53:26.558202   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:53:36.587446   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:53:46.620690   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:53:56.651472   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
W0925 05:54:06.681386   12496 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:54:16.733928   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:54:26.780811   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:54:36.844287   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:54:46.875147   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:54:56.920833   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:55:06.965198   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:55:17.011500   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:55:27.057891   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:55:37.092777   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:55:47.143854   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:55:57.179436   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:56:07.216769   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
W0925 05:56:17.245506   12496 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:56:27.288207   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:56:37.325658   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

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
W0925 05:56:47.357988   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-052abbec77db8e0af				machine "i-052abbec77db8e0af" has not yet joined cluster
Machine	i-0e68ac0f911d5fa7a				machine "i-0e68ac0f911d5fa7a" has not yet joined cluster
Machine	i-0fca60ab7fcbdb01a				machine "i-0fca60ab7fcbdb01a" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-jdb4w		system-cluster-critical pod "coredns-5dc785954d-jdb4w" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8vzdw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8vzdw" is pending

Validation Failed
W0925 05:57:01.400117   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-wvkr8				system-node-critical pod "ebs-csi-node-wvkr8" is pending
Pod	kube-system/ebs-csi-node-zz8h6				system-node-critical pod "ebs-csi-node-zz8h6" is pending
Pod	kube-system/weave-net-bx4z2				system-node-critical pod "weave-net-bx4z2" is pending
Pod	kube-system/weave-net-ssg4b				system-node-critical pod "weave-net-ssg4b" is pending
Pod	kube-system/weave-net-wlbws				system-node-critical pod "weave-net-wlbws" is pending

Validation Failed
W0925 05:57:14.078128   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 11 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w		system-cluster-critical pod "coredns-5dc785954d-jdb4w" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8vzdw	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8vzdw" is pending
Pod	kube-system/ebs-csi-node-kvj44			system-node-critical pod "ebs-csi-node-kvj44" is pending
Pod	kube-system/ebs-csi-node-wvkr8			system-node-critical pod "ebs-csi-node-wvkr8" is pending
Pod	kube-system/ebs-csi-node-zz8h6			system-node-critical pod "ebs-csi-node-zz8h6" is pending

Validation Failed
W0925 05:57:26.628835   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 12 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w		system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7			system-node-critical pod "ebs-csi-node-k7dd7" is pending
Pod	kube-system/ebs-csi-node-wvkr8			system-node-critical pod "ebs-csi-node-wvkr8" is pending
Pod	kube-system/ebs-csi-node-zz8h6			system-node-critical pod "ebs-csi-node-zz8h6" is pending
Pod	kube-system/weave-net-7ln5c			system-node-critical pod "weave-net-7ln5c" is pending

Validation Failed
W0925 05:57:39.186232   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is pending

Validation Failed
W0925 05:57:51.757774   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w					system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-32-56.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-56.ap-northeast-2.compute.internal" is pending

Validation Failed
W0925 05:58:04.323547   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w					system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-wvkr8						system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/kube-proxy-ip-172-20-62-212.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-62-212.ap-northeast-2.compute.internal" is pending

Validation Failed
W0925 05:58:17.020679   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 05:58:29.615855   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 05:58:42.226400   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 05:58:54.868824   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 05:59:07.516617   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 05:59:20.436410   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 05:59:33.133971   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 05:59:45.921638   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 05:59:58.590632   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 06:00:11.226725   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 06:00:23.935059   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-63-75.ap-northeast-2.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)

Validation Failed
W0925 06:00:36.580057   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:00:49.086586   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:01:02.199550   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:01:14.861851   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:01:27.475838   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:01:40.136071   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:01:52.887976   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:02:05.499284   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)

Validation Failed
W0925 06:02:18.175114   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:02:30.921487   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:02:43.538469   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:02:56.115923   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:03:08.873078   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:03:21.518776   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:03:34.177653   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:03:46.842337   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:03:59.465959   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:04:12.090558   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:04:24.754651   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:04:37.392591   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:04:49.968460   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:05:03.305837   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)

Validation Failed
W0925 06:05:16.070593   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)

Validation Failed
W0925 06:05:28.680143   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)

Validation Failed
W0925 06:05:41.321500   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:05:53.921535   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:06:06.613582   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:06:19.251880   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:06:31.924219   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:06:44.570588   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:06:57.097959   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:07:09.755149   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:07:22.315578   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:07:35.011028   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:07:47.749371   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-jdb4w	system-cluster-critical pod "coredns-5dc785954d-jdb4w" is not ready (coredns)
Pod	kube-system/ebs-csi-node-k7dd7		system-node-critical pod "ebs-csi-node-k7dd7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-kvj44		system-node-critical pod "ebs-csi-node-kvj44" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wvkr8		system-node-critical pod "ebs-csi-node-wvkr8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zz8h6		system-node-critical pod "ebs-csi-node-zz8h6" is not ready (ebs-plugin)

Validation Failed
W0925 06:08:00.416966   12496 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0925 06:08:10.423006    4856 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0925 06:08:10.449465   12508 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 06:08:10.450660   12508 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/25 06:08:22 Dumping node ip-172-20-32-56.ap-northeast-2.compute.internal
2021/09/25 06:08:29 Dumping node ip-172-20-49-36.ap-northeast-2.compute.internal
2021/09/25 06:08:36 Dumping node ip-172-20-53-255.ap-northeast-2.compute.internal
... skipping 1443 lines ...
route-table:rtb-01bba0635203641b5	ok
vpc:vpc-0953461dfe2e5fd31	ok
dhcp-options:dopt-0632035d6e00ccd90	ok
Deleted kubectl config for e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

Deleted cluster: "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...