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

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0914 10:26:00.756572    4084 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0914 10:26:00.758182    4084 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.2+v1.22.0-beta.1-62-gbf2982413f/linux/amd64/kops
I0914 10:26:01.833948    4084 up.go:43] Cleaning up any leaked resources from previous cluster
I0914 10:26:01.833988    4084 dumplogs.go:38] /logs/artifacts/f80691dd-1545-11ec-840b-fe625b2855d5/kops toolbox dump --name e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0914 10:26:01.851293    4104 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 10:26:01.851692    4104 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io" not found
W0914 10:26:02.378338    4084 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0914 10:26:02.378412    4084 down.go:48] /logs/artifacts/f80691dd-1545-11ec-840b-fe625b2855d5/kops delete cluster --name e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io --yes
I0914 10:26:02.396150    4114 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 10:26:02.397094    4114 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io" not found
I0914 10:26:03.037939    4084 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/14 10:26:03 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
I0914 10:26:03.047009    4084 http.go:37] curl https://ip.jsb.workers.dev
I0914 10:26:03.137449    4084 up.go:144] /logs/artifacts/f80691dd-1545-11ec-840b-fe625b2855d5/kops create cluster --name e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.10 --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.70.224.157/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0914 10:26:03.154197    4124 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 10:26:03.154553    4124 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0914 10:26:03.178500    4124 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0914 10:26:03.648913    4124 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 41 lines ...

I0914 10:26:32.027028    4084 up.go:181] /logs/artifacts/f80691dd-1545-11ec-840b-fe625b2855d5/kops validate cluster --name e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0914 10:26:32.046854    4146 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 10:26:32.047118    4146 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io

W0914 10:26:33.517168    4146 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0392ba74fa-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-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0914 10:31:44.839647    4146 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 8 lines ...
Machine	i-0607d9be276beb088					machine "i-0607d9be276beb088" has not yet joined cluster
Machine	i-0c7f484b66de631ca					machine "i-0c7f484b66de631ca" has not yet joined cluster
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sgf52		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sgf52" is pending

Validation Failed
W0914 10:31:59.100532    4146 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 15 lines ...
Pod	kube-system/calico-node-czbzc				system-node-critical pod "calico-node-czbzc" is pending
Pod	kube-system/calico-node-n4wb2				system-node-critical pod "calico-node-n4wb2" is pending
Pod	kube-system/calico-node-smth5				system-node-critical pod "calico-node-smth5" is pending
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sgf52		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sgf52" is pending

Validation Failed
W0914 10:32:11.764089    4146 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-czbzc				system-node-critical pod "calico-node-czbzc" is not ready (calico-node)
Pod	kube-system/calico-node-n4wb2				system-node-critical pod "calico-node-n4wb2" is pending
Pod	kube-system/calico-node-smth5				system-node-critical pod "calico-node-smth5" is pending
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sgf52		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sgf52" is pending

Validation Failed
W0914 10:32:24.429980    4146 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-czbzc				system-node-critical pod "calico-node-czbzc" is not ready (calico-node)
Pod	kube-system/calico-node-n4wb2				system-node-critical pod "calico-node-n4wb2" is not ready (calico-node)
Pod	kube-system/calico-node-smth5				system-node-critical pod "calico-node-smth5" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-sgf52		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-sgf52" is pending

Validation Failed
W0914 10:32:37.213552    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:32:49.911734    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:33:02.469071    4146 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 9 lines ...
KIND	NAME									MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw			system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk					system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt					system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-49-204.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-49-204.ap-northeast-2.compute.internal" is pending

Validation Failed
W0914 10:33:15.062987    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:33:27.766213    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:33:40.375041    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:33:52.975065    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:34:05.566761    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:34:18.190245    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:34:31.199013    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:34:43.897566    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:34:56.682886    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:35:09.313305    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:35:21.990428    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:35:34.589645    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:35:47.184280    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:36:00.417162    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:36:13.071718    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:36:25.707796    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:36:38.446662    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:36:51.053515    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:37:03.744412    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:37:16.461487    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:37:29.143382    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:37:41.791145    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:37:54.515018    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:38:07.419876    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:38:20.127342    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:38:33.083118    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:38:45.701824    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:38:58.240800    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:39:11.014041    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:39:23.701221    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:39:36.396114    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:39:49.031373    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:40:02.272420    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:40:14.913368    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:40:27.816880    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:40:40.494315    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:40:53.134492    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:41:05.744634    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:41:18.448327    4146 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-gcpcw	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-gcpcw" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-qdvmk			system-cluster-critical pod "coredns-64497985bd-qdvmk" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-t8nrt			system-cluster-critical pod "coredns-64497985bd-t8nrt" is not ready (coredns)

Validation Failed
W0914 10:41:31.104284    4146 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0914 10:41:41.108786    4084 dumplogs.go:38] /logs/artifacts/f80691dd-1545-11ec-840b-fe625b2855d5/kops toolbox dump --name e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0914 10:41:41.128312    4156 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 10:41:41.128429    4156 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/14 10:41:53 Dumping node ip-172-20-34-219.ap-northeast-2.compute.internal
2021/09/14 10:42:00 Dumping node ip-172-20-48-25.ap-northeast-2.compute.internal
2021/09/14 10:42:06 Dumping node ip-172-20-48-52.ap-northeast-2.compute.internal
... skipping 1445 lines ...
route-table:rtb-024614a609a14ce6a	ok
vpc:vpc-09200a2a44bc85665	ok
dhcp-options:dopt-02b12daa6d4448ffa	ok
Deleted kubectl config for e2e-0392ba74fa-30dcb.test-cncf-aws.k8s.io

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