This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-05 01:08
Elapsed20m13s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1005 01:09:18.453783    4710 up.go:43] Cleaning up any leaked resources from previous cluster
I1005 01:09:18.453825    4710 dumplogs.go:40] /logs/artifacts/a257d069-2578-11ec-b80b-66e31101aeea/kops toolbox dump --name e2e-7ad2319071-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1005 01:09:18.478286    4732 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1005 01:09:18.478412    4732 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-7ad2319071-99215.test-cncf-aws.k8s.io" not found
W1005 01:09:19.015788    4710 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1005 01:09:19.016024    4710 down.go:48] /logs/artifacts/a257d069-2578-11ec-b80b-66e31101aeea/kops delete cluster --name e2e-7ad2319071-99215.test-cncf-aws.k8s.io --yes
I1005 01:09:19.036826    4742 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1005 01:09:19.038435    4742 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-7ad2319071-99215.test-cncf-aws.k8s.io" not found
I1005 01:09:19.613610    4710 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/05 01:09:19 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
I1005 01:09:19.622129    4710 http.go:37] curl https://ip.jsb.workers.dev
I1005 01:09:19.713785    4710 up.go:144] /logs/artifacts/a257d069-2578-11ec-b80b-66e31101aeea/kops create cluster --name e2e-7ad2319071-99215.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --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 35.192.90.167/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I1005 01:09:19.740756    4753 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1005 01:09:19.742310    4753 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1005 01:09:19.807289    4753 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1005 01:09:20.458174    4753 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I1005 01:09:49.917867    4710 up.go:181] /logs/artifacts/a257d069-2578-11ec-b80b-66e31101aeea/kops validate cluster --name e2e-7ad2319071-99215.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1005 01:09:49.939247    4774 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1005 01:09:49.939367    4774 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-7ad2319071-99215.test-cncf-aws.k8s.io

W1005 01:09:51.556384    4774 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7ad2319071-99215.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1005 01:10:01.595366    4774 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7ad2319071-99215.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
W1005 01:10:11.642269    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:10:21.690437    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:10:31.721854    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:10:41.750231    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:10:51.786071    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:11:01.823038    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:11:11.858410    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:11:21.889049    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:11:31.920204    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:11:41.968410    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:11:52.015311    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:12:02.059902    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:12:12.124756    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:12:22.162183    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:12:32.196683    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:12:42.233451    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:12:52.262228    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:13:02.313371    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:13:12.343728    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:13:22.378584    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:13:32.432441    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:13:42.469056    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:13:52.501139    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:14:02.532998    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:14:12.564775    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:14:22.631170    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:14:32.669718    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:14:42.704086    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:14:52.745833    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:15:02.785519    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:15:12.817220    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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
W1005 01:15:22.851047    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/calico-kube-controllers-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is pending
Pod	kube-system/calico-node-lj6sr				system-node-critical pod "calico-node-lj6sr" is not ready (calico-node)
Pod	kube-system/calico-node-skpp5				system-node-critical pod "calico-node-skpp5" is pending
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rv5hb		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rv5hb" is pending

Validation Failed
W1005 01:15:36.814269    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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 17 lines ...
Pod	kube-system/calico-node-skpp5						system-node-critical pod "calico-node-skpp5" is pending
Pod	kube-system/calico-node-v9wn7						system-node-critical pod "calico-node-v9wn7" is pending
Pod	kube-system/coredns-5dc785954d-mss9l					system-cluster-critical pod "coredns-5dc785954d-mss9l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rv5hb				system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rv5hb" is pending
Pod	kube-system/kube-proxy-ip-172-20-34-127.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-34-127.ap-northeast-2.compute.internal" is pending

Validation Failed
W1005 01:15:49.467054    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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 14 lines ...
Pod	kube-system/calico-node-97qh9				system-node-critical pod "calico-node-97qh9" is pending
Pod	kube-system/calico-node-skpp5				system-node-critical pod "calico-node-skpp5" is not ready (calico-node)
Pod	kube-system/calico-node-v9wn7				system-node-critical pod "calico-node-v9wn7" is pending
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rv5hb		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rv5hb" is pending

Validation Failed
W1005 01:16:02.204719    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-97qh9				system-node-critical pod "calico-node-97qh9" is not ready (calico-node)
Pod	kube-system/calico-node-skpp5				system-node-critical pod "calico-node-skpp5" is not ready (calico-node)
Pod	kube-system/calico-node-v9wn7				system-node-critical pod "calico-node-v9wn7" is not ready (calico-node)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is pending
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is pending

Validation Failed
W1005 01:16:14.905118    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:16:27.540673    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:16:40.164042    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:16:52.858650    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:17:05.561801    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:17:18.219234    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:17:30.895553    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:17:43.743437    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:17:56.510184    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:18:09.179465    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:18:21.828642    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:18:34.568621    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:18:47.170102    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:18:59.856603    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:19:12.533504    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:19:25.429640    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:19:38.672595    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:19:51.297409    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:20:04.006906    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:20:16.655490    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:20:29.836854    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:20:42.645897    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:20:55.237917    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:21:08.166651    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:21:20.746388    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:21:33.471488    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:21:46.052196    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:21:58.736715    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:22:11.459019    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:22:24.152169    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:22:36.776526    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:22:49.513797    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:23:02.141085    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:23:14.871062    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:23:27.456035    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:23:40.674073    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:23:53.306025    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:24:06.095557    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:24:18.823213    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:24:31.551016    4774 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
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-6b59cd85f8-q8qnk	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-q8qnk" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-mss9l			system-cluster-critical pod "coredns-5dc785954d-mss9l" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-nwdxs			system-cluster-critical pod "coredns-5dc785954d-nwdxs" is not ready (coredns)

Validation Failed
W1005 01:24:44.305338    4774 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1005 01:24:54.317918    4710 dumplogs.go:40] /logs/artifacts/a257d069-2578-11ec-b80b-66e31101aeea/kops toolbox dump --name e2e-7ad2319071-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1005 01:24:54.335151    4785 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1005 01:24:54.335566    4785 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/05 01:25:07 Dumping node ip-172-20-34-127.ap-northeast-2.compute.internal
2021/10/05 01:25:13 Dumping node ip-172-20-38-140.ap-northeast-2.compute.internal
2021/10/05 01:25:18 Dumping node ip-172-20-43-251.ap-northeast-2.compute.internal
... skipping 1409 lines ...
route-table:rtb-092c45e1cf6edaa1a	ok
vpc:vpc-03659f17005f014e4	ok
dhcp-options:dopt-073968cf9c7a9d063	ok
Deleted kubectl config for e2e-7ad2319071-99215.test-cncf-aws.k8s.io

Deleted cluster: "e2e-7ad2319071-99215.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace