This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-15 23:49
Elapsed20m40s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 129 lines ...
I0915 23:50:18.875971    4100 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-138-gd9f21f94af/linux/amd64/kops
I0915 23:50:19.791021    4100 up.go:43] Cleaning up any leaked resources from previous cluster
I0915 23:50:19.791054    4100 dumplogs.go:38] /logs/artifacts/80d37edc-167f-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0915 23:50:19.808071    4119 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 23:50:19.808318    4119 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0915 23:50:19.808353    4119 featureflag.go:166] FeatureFlag "AWSIPv6"=true
Error: Cluster.kops.k8s.io "e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io" not found
W0915 23:50:20.314357    4100 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0915 23:50:20.314403    4100 down.go:48] /logs/artifacts/80d37edc-167f-11ec-a0c8-aafcb65c973d/kops delete cluster --name e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io --yes
I0915 23:50:20.332032    4128 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 23:50:20.332192    4128 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0915 23:50:20.332201    4128 featureflag.go:166] FeatureFlag "AWSIPv6"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io" not found
I0915 23:50:20.818825    4100 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/15 23:50:20 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
I0915 23:50:20.826660    4100 http.go:37] curl https://ip.jsb.workers.dev
I0915 23:50:20.940903    4100 up.go:144] /logs/artifacts/80d37edc-167f-11ec-a0c8-aafcb65c973d/kops create cluster --name e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.2.26+49e00c006cc2af --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=calico --container-runtime=containerd --ipv6 --api-loadbalancer-type=public --api-loadbalancer-class=network --set=cluster.spec.api.loadBalancer.useForInternalApi=true --set=cluster.spec.cloudControllerManager.cloudProvider=aws --set=cluster.spec.nonMasqueradeCIDR=fd00:10:96::/64 --admin-access 34.68.229.223/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0915 23:50:20.958321    4138 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 23:50:20.959289    4138 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0915 23:50:20.959295    4138 featureflag.go:166] FeatureFlag "AWSIPv6"=true
I0915 23:50:20.982946    4138 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
... skipping 33 lines ...
I0915 23:50:42.081292    4100 up.go:181] /logs/artifacts/80d37edc-167f-11ec-a0c8-aafcb65c973d/kops validate cluster --name e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0915 23:50:42.097775    4158 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0915 23:50:42.098685    4158 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0915 23:50:42.098831    4158 featureflag.go:166] FeatureFlag "AWSIPv6"=true
Validating cluster e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io

W0915 23:50:43.763664    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:50:53.793581    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:51:03.838791    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:51:13.868789    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:51:23.928208    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:51:33.980693    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:51:44.008784    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:51:54.044972    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:52:04.094127    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:52:14.132198    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:52:24.163731    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:52:34.198790    4158 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:52:44.450973    4158 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp: lookup api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0915 23:52:54.533463    4158 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp [2406:da12:38e:c001:8a31:760b:4438:97bb]:443: connect: network is unreachable
W0915 23:53:34.569455    4158 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 13.125.185.215:443: i/o timeout
W0915 23:53:44.641125    4158 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp [2406:da12:38e:c001:8a31:760b:4438:97bb]:443: connect: network is unreachable
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 13 lines ...
Pod	kube-system/dns-controller-6dd7cb5b5d-bg7l5					system-cluster-critical pod "dns-controller-6dd7cb5b5d-bg7l5" is pending
Pod	kube-system/ebs-csi-controller-65ddbb89db-2j474					system-cluster-critical pod "ebs-csi-controller-65ddbb89db-2j474" is pending
Pod	kube-system/ebs-csi-node-dspw5							system-node-critical pod "ebs-csi-node-dspw5" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-33-79.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is pending

Validation Failed
W0915 23:54:06.245201    4158 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 ...
Pod	kube-system/calico-node-rfncj				system-node-critical pod "calico-node-rfncj" is pending
Pod	kube-system/coredns-5dc785954d-9tvj5			system-cluster-critical pod "coredns-5dc785954d-9tvj5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6fpwg		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6fpwg" is pending
Pod	kube-system/ebs-csi-controller-65ddbb89db-2j474		system-cluster-critical pod "ebs-csi-controller-65ddbb89db-2j474" is pending
Pod	kube-system/ebs-csi-node-dspw5				system-node-critical pod "ebs-csi-node-dspw5" is pending

Validation Failed
W0915 23:54:18.975804    4158 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 ...
Pod	kube-system/calico-node-rfncj				system-node-critical pod "calico-node-rfncj" is pending
Pod	kube-system/coredns-5dc785954d-9tvj5			system-cluster-critical pod "coredns-5dc785954d-9tvj5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6fpwg		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6fpwg" is pending
Pod	kube-system/ebs-csi-controller-65ddbb89db-2j474		system-cluster-critical pod "ebs-csi-controller-65ddbb89db-2j474" is pending
Pod	kube-system/ebs-csi-node-dspw5				system-node-critical pod "ebs-csi-node-dspw5" is pending

Validation Failed
W0915 23:54:31.629139    4158 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 10 lines ...
Pod	kube-system/calico-kube-controllers-58497c65d5-qvwgl	system-cluster-critical pod "calico-kube-controllers-58497c65d5-qvwgl" is pending
Pod	kube-system/coredns-5dc785954d-9tvj5			system-cluster-critical pod "coredns-5dc785954d-9tvj5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6fpwg		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6fpwg" is pending
Pod	kube-system/ebs-csi-controller-65ddbb89db-2j474		system-cluster-critical pod "ebs-csi-controller-65ddbb89db-2j474" is pending
Pod	kube-system/ebs-csi-node-dspw5				system-node-critical pod "ebs-csi-node-dspw5" is pending

Validation Failed
W0915 23:54:44.319302    4158 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 ...
Pod	kube-system/coredns-5dc785954d-9tvj5			system-cluster-critical pod "coredns-5dc785954d-9tvj5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6fpwg		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6fpwg" is pending
Pod	kube-system/ebs-csi-controller-65ddbb89db-2j474		system-cluster-critical pod "ebs-csi-controller-65ddbb89db-2j474" is pending
Pod	kube-system/ebs-csi-node-78dvr				system-node-critical pod "ebs-csi-node-78dvr" is pending
Pod	kube-system/ebs-csi-node-bz7pr				system-node-critical pod "ebs-csi-node-bz7pr" is pending

Validation Failed
W0915 23:54:57.071595    4158 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 19 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6fpwg		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6fpwg" is pending
Pod	kube-system/ebs-csi-node-6lgjn				system-node-critical pod "ebs-csi-node-6lgjn" is pending
Pod	kube-system/ebs-csi-node-78dvr				system-node-critical pod "ebs-csi-node-78dvr" is pending
Pod	kube-system/ebs-csi-node-bz7pr				system-node-critical pod "ebs-csi-node-bz7pr" is pending
Pod	kube-system/ebs-csi-node-nmtb7				system-node-critical pod "ebs-csi-node-nmtb7" is pending

Validation Failed
W0915 23:55:09.882535    4158 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 16 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-6fpwg		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-6fpwg" is pending
Pod	kube-system/ebs-csi-node-6lgjn				system-node-critical pod "ebs-csi-node-6lgjn" is pending
Pod	kube-system/ebs-csi-node-78dvr				system-node-critical pod "ebs-csi-node-78dvr" is pending
Pod	kube-system/ebs-csi-node-bz7pr				system-node-critical pod "ebs-csi-node-bz7pr" is pending
Pod	kube-system/ebs-csi-node-nmtb7				system-node-critical pod "ebs-csi-node-nmtb7" is pending

Validation Failed
W0915 23:55:22.524909    4158 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 11 lines ...
Pod	kube-system/calico-node-mnlfh	system-node-critical pod "calico-node-mnlfh" is not ready (calico-node)
Pod	kube-system/ebs-csi-node-6lgjn	system-node-critical pod "ebs-csi-node-6lgjn" is pending
Pod	kube-system/ebs-csi-node-78dvr	system-node-critical pod "ebs-csi-node-78dvr" is pending
Pod	kube-system/ebs-csi-node-bz7pr	system-node-critical pod "ebs-csi-node-bz7pr" is pending
Pod	kube-system/ebs-csi-node-nmtb7	system-node-critical pod "ebs-csi-node-nmtb7" is pending

Validation Failed
W0915 23:55:35.256194    4158 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 81 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:56:51.508529    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:57:04.301944    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:57:16.936478    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:57:29.553435    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:57:42.340476    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:57:55.592329    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:58:08.314883    4158 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 36 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:58:46.722184    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:58:59.452638    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:59:12.231601    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:59:24.802251    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:59:37.386148    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0915 23:59:50.003842    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:00:03.027827    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:00:15.670219    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:00:28.289141    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:00:40.968547    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:00:53.637552    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:01:06.307582    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:01:18.982511    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:01:31.638786    4158 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 51 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:02:23.385540    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:02:35.981017    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:02:48.698757    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:03:01.314064    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:03:14.050989    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:03:26.684925    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:03:39.348584    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:03:51.956559    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:04:04.646917    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:04:17.275809    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:04:30.011143    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:04:42.733056    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:04:55.446961    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:05:08.073425    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:05:20.762021    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:05:33.546483    4158 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 6 lines ...
ip-172-20-55-239.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME										MESSAGE
Pod	kube-system/kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal	system-cluster-critical pod "kube-scheduler-ip-172-20-33-79.ap-northeast-2.compute.internal" is not ready (kube-scheduler)

Validation Failed
W0916 00:05:46.087523    4158 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0916 00:05:56.101090    4100 dumplogs.go:38] /logs/artifacts/80d37edc-167f-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0916 00:05:56.122562    4168 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 00:05:56.122664    4168 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 00:05:56.122670    4168 featureflag.go:166] FeatureFlag "AWSIPv6"=true
2021/09/16 00:06:08 Dumping node ip-172-20-33-12.ap-northeast-2.compute.internal
2021/09/16 00:06:16 Dumping node ip-172-20-33-79.ap-northeast-2.compute.internal
... skipping 1574 lines ...
route-table:rtb-0e3910c922eaecbdb	ok
vpc:vpc-0962328ad28110dcb	ok
dhcp-options:dopt-0ff669e0b1b6403f0	ok
Deleted kubectl config for e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io

Deleted cluster: "e2e-81c860e6e0-fbf9c.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace