This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-21 10:25
Elapsed20m17s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 132 lines ...
I0921 10:26:00.347425    4675 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0921 10:26:00.349200    4675 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.2+v1.22.0-beta.1-99-g92400cd674/linux/amd64/kops
I0921 10:26:01.193844    4675 up.go:43] Cleaning up any leaked resources from previous cluster
I0921 10:26:01.193884    4675 dumplogs.go:40] /logs/artifacts/210367b0-1ac6-11ec-8e49-8acb7ceab3aa/kops toolbox dump --name e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0921 10:26:01.213190    4695 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0921 10:26:01.213733    4695 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io" not found
W0921 10:26:01.713125    4675 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0921 10:26:01.713200    4675 down.go:48] /logs/artifacts/210367b0-1ac6-11ec-8e49-8acb7ceab3aa/kops delete cluster --name e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io --yes
I0921 10:26:01.734062    4705 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0921 10:26:01.734168    4705 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io" not found
I0921 10:26:02.220254    4675 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/21 10:26:02 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
I0921 10:26:02.228246    4675 http.go:37] curl https://ip.jsb.workers.dev
I0921 10:26:02.307709    4675 up.go:144] /logs/artifacts/210367b0-1ac6-11ec-8e49-8acb7ceab3aa/kops create cluster --name e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.72.239.94/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0921 10:26:02.326847    4714 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0921 10:26:02.326958    4714 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0921 10:26:02.351100    4714 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0921 10:26:02.845750    4714 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 41 lines ...

I0921 10:26:31.649408    4675 up.go:181] /logs/artifacts/210367b0-1ac6-11ec-8e49-8acb7ceab3aa/kops validate cluster --name e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0921 10:26:31.669915    4733 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0921 10:26:31.670011    4733 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io

W0921 10:26:33.142167    4733 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:26:43.172252    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:26:53.209354    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:27:03.279167    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:27:13.311856    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:27:23.425067    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:27:33.459205    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:27:43.495816    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:27:53.526553    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
W0921 10:28:03.560037    4733 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:28:13.620602    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:28:23.679286    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:28:33.707995    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:28:43.740792    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:28:53.777291    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:29:03.806499    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:29:13.836501    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:29:23.874280    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:29:33.903378    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:29:43.966546    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:29:53.996001    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:30:04.027238    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
W0921 10:30:14.097038    4733 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:30:24.143109    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:30:34.183168    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:30:44.216590    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:30:54.249358    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:31:04.280647    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:31:14.324056    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0921 10:31:24.359981    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
W0921 10:32:04.400746    4733 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-74af9e8c27-30dcb.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-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
... skipping 12 lines ...
Pod	kube-system/calico-node-h2r25				system-node-critical pod "calico-node-h2r25" is not ready (calico-node)
Pod	kube-system/calico-node-nm7ng				system-node-critical pod "calico-node-nm7ng" is not ready (calico-node)
Pod	kube-system/calico-node-pdcwq				system-node-critical pod "calico-node-pdcwq" is pending
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-9dm9v		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-9dm9v" is pending

Validation Failed
W0921 10:32:17.971639    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-pdcwq				system-node-critical pod "calico-node-pdcwq" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is pending

Validation Failed
W0921 10:32:30.302590    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME									MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq			system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9					system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb					system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-52-154.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-154.ap-northeast-1.compute.internal" is pending

Validation Failed
W0921 10:32:42.812456    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:32:55.271776    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:33:07.708125    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:33:20.000339    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:33:32.298497    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:33:44.645172    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:33:56.961275    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:34:09.197949    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:34:21.745434    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:34:34.163110    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:34:46.438671    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:34:58.921466    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:35:11.296202    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:35:23.700572    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:35:36.025556    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:35:48.504523    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:36:00.830471    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:36:13.629439    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:36:25.963603    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:36:38.255430    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:36:50.536552    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:37:02.838387    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:37:15.320134    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:37:27.972553    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:37:40.516768    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:37:52.944685    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:38:05.296459    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:38:17.665245    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:38:29.991187    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:38:42.365650    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:38:54.718138    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:39:07.091529    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:39:19.407858    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:39:31.929461    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:39:44.220778    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:39:56.537792    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:40:09.305965    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:40:21.673596    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:40:34.092561    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:40:46.427618    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:40:58.758188    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:41:11.147457    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-855445d444-rm2gq	system-cluster-critical pod "calico-kube-controllers-855445d444-rm2gq" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-8vrn9			system-cluster-critical pod "coredns-64497985bd-8vrn9" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-vfsdb			system-cluster-critical pod "coredns-64497985bd-vfsdb" is not ready (coredns)

Validation Failed
W0921 10:41:23.512148    4733 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0921 10:41:33.524936    4675 dumplogs.go:40] /logs/artifacts/210367b0-1ac6-11ec-8e49-8acb7ceab3aa/kops toolbox dump --name e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0921 10:41:33.545195    4743 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0921 10:41:33.546104    4743 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/21 10:41:45 Dumping node ip-172-20-33-64.ap-northeast-1.compute.internal
2021/09/21 10:41:50 Dumping node ip-172-20-44-62.ap-northeast-1.compute.internal
2021/09/21 10:41:54 Dumping node ip-172-20-48-143.ap-northeast-1.compute.internal
... skipping 1467 lines ...
route-table:rtb-090aa75cb5dd56825	ok
vpc:vpc-023e47c59add0289e	ok
dhcp-options:dopt-018a8030c2c393878	ok
Deleted kubectl config for e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io

Deleted cluster: "e2e-74af9e8c27-30dcb.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace