This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-16 18:14
Elapsed20m33s
Revisionmaster

Test Failures


kubetest2 Up 16m7s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 159 lines ...
I0716 18:16:05.673644    6066 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0716 18:16:05.675520    6066 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-80-gb7d4499629/linux/amd64/kops
I0716 18:16:07.026214    6066 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519
I0716 18:16:07.035150    6066 up.go:44] Cleaning up any leaked resources from previous cluster
I0716 18:16:07.035273    6066 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops toolbox dump --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin
I0716 18:16:07.035293    6066 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops toolbox dump --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin
W0716 18:16:07.575306    6066 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0716 18:16:07.575468    6066 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops delete cluster --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --yes
I0716 18:16:07.575513    6066 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops delete cluster --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --yes
I0716 18:16:07.623502    6100 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io" not found
I0716 18:16:08.109087    6066 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/16 18:16:08 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
I0716 18:16:08.124366    6066 http.go:37] curl https://ip.jsb.workers.dev
I0716 18:16:08.225934    6066 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops create cluster --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=136693071363/debian-10-amd64-20220328-962 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.226.88.85/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0716 18:16:08.225985    6066 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops create cluster --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=136693071363/debian-10-amd64-20220328-962 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.226.88.85/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0716 18:16:08.261031    6110 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0716 18:16:08.306638    6110 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0716 18:16:08.871008    6110 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 529 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
W0716 18:17:00.930552    6151 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.medium	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
W0716 18:17:10.972765    6151 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.medium	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
W0716 18:17:21.021430    6151 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.medium	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
W0716 18:17:31.059524    6151 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.medium	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
W0716 18:17:41.096367    6151 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.medium	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
W0716 18:17:51.135685    6151 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.medium	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
W0716 18:18:01.177437    6151 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.medium	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
W0716 18:18:11.216467    6151 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.medium	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
W0716 18:18:21.250630    6151 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.medium	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
W0716 18:18:31.285588    6151 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.medium	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
W0716 18:18:41.334577    6151 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.medium	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
W0716 18:18:51.389799    6151 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.medium	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
W0716 18:19:01.431965    6151 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.medium	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
W0716 18:19:11.480515    6151 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.medium	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
W0716 18:19:21.525117    6151 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.medium	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
W0716 18:19:31.563497    6151 validate_cluster.go:232] (will retry): cluster not yet healthy
W0716 18:20:11.600008    6151 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
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.medium	4	4	ap-northeast-2a

NODE STATUS
... skipping 11 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:20:25.868076    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:20:38.677807    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:20:51.482017    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:21:04.310330    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:21:17.195881    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:21:30.013763    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:21:42.945163    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:21:55.845597    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:22:08.702429    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:22:21.584416    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:22:34.446482    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:22:47.292698    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:23:00.227960    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:23:13.382768    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:23:26.189863    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:23:39.195630    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:23:52.029168    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:24:04.908112    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:24:18.353099    6151 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.medium	4	4	ap-northeast-2a

... skipping 13 lines ...
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/cilium-operator-598c4558db-sf6zb		system-cluster-critical pod "cilium-operator-598c4558db-sf6zb" is pending
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:24:31.326121    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:24:44.176332    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:24:56.985413    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:25:09.881357    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:25:22.743758    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:25:35.577997    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:25:48.525013    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:26:01.499697    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:26:14.396854    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:26:27.242993    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:26:40.239470    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:26:53.017621    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:27:05.888462    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:27:18.773032    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:27:31.523744    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:27:44.366024    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:27:57.224333    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:28:10.880444    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:28:23.758212    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:28:36.576579    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:28:49.596644    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:29:02.393004    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:29:15.347453    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:29:28.227705    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:29:41.238796    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:29:54.057614    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:30:06.995094    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:30:19.895322    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:30:32.743826    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:30:45.634257    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:30:58.449570    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:31:11.343885    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:31:24.163977    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:31:37.044191    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:31:49.952019    6151 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.medium	4	4	ap-northeast-2a

... skipping 12 lines ...
Node	ip-172-20-40-221.ap-northeast-2.compute.internal	node "ip-172-20-40-221.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-51-192.ap-northeast-2.compute.internal	node "ip-172-20-51-192.ap-northeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-63-250.ap-northeast-2.compute.internal	node "ip-172-20-63-250.ap-northeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5fcc7b6498-4tpbg			system-cluster-critical pod "coredns-5fcc7b6498-4tpbg" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-st4th		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-st4th" is pending

Validation Failed
W0716 18:32:03.419609    6151 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0716 18:32:13.425347    6066 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops toolbox dump --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin
I0716 18:32:13.425402    6066 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops toolbox dump --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin
I0716 18:33:09.404534    6066 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops get cluster --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io -o yaml
I0716 18:33:09.404569    6066 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops get cluster --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io -o yaml
I0716 18:33:09.915292    6066 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops get instancegroups --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io -o yaml
I0716 18:33:09.915327    6066 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/13d87870-0533-11ed-ad40-226d46f65466/kops get instancegroups --name e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io -o yaml
... skipping 267 lines ...
route-table:rtb-053b5f10d2d59acfa	ok
vpc:vpc-0a864d93a29acbefb	ok
dhcp-options:dopt-03ed02ad7a51a8450	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-deb10-k22-docker.test-cncf-aws.k8s.io

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