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 08:40
Elapsed19m23s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0914 08:41:52.135121    4093 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0914 08:41:52.137760    4093 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 08:41:53.868433    4093 up.go:43] Cleaning up any leaked resources from previous cluster
I0914 08:41:53.868595    4093 dumplogs.go:38] /logs/artifacts/4cd74601-1537-11ec-840b-fe625b2855d5/kops toolbox dump --name e2e-7230299cf8-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0914 08:41:53.940290    4114 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 08:41:53.940724    4114 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-7230299cf8-ec357.test-cncf-aws.k8s.io" not found
W0914 08:41:54.631422    4093 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0914 08:41:54.631507    4093 down.go:48] /logs/artifacts/4cd74601-1537-11ec-840b-fe625b2855d5/kops delete cluster --name e2e-7230299cf8-ec357.test-cncf-aws.k8s.io --yes
I0914 08:41:54.699118    4124 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 08:41:54.699245    4124 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-7230299cf8-ec357.test-cncf-aws.k8s.io" not found
I0914 08:41:55.302226    4093 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/14 08:41:55 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 08:41:55.314501    4093 http.go:37] curl https://ip.jsb.workers.dev
I0914 08:41:55.417477    4093 up.go:144] /logs/artifacts/4cd74601-1537-11ec-840b-fe625b2855d5/kops create cluster --name e2e-7230299cf8-ec357.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=docker --admin-access 34.136.150.248/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0914 08:41:55.490233    4134 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 08:41:55.490458    4134 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0914 08:41:55.583380    4134 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0914 08:41:56.332887    4134 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 41 lines ...

I0914 08:42:26.420450    4093 up.go:181] /logs/artifacts/4cd74601-1537-11ec-840b-fe625b2855d5/kops validate cluster --name e2e-7230299cf8-ec357.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0914 08:42:26.467250    4152 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 08:42:26.467386    4152 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-7230299cf8-ec357.test-cncf-aws.k8s.io

W0914 08:42:28.086691    4152 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7230299cf8-ec357.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0914 08:42:38.137933    4152 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7230299cf8-ec357.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0914 08:45:09.336948    4152 validate_cluster.go:232] (will retry): cluster not yet healthy
W0914 08:45:19.355279    4152 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-7230299cf8-ec357.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 10 lines ...
Node	ip-172-20-58-182.ap-northeast-1.compute.internal	node "ip-172-20-58-182.ap-northeast-1.compute.internal" of role "node" is not ready
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-znc8h				system-node-critical pod "calico-node-znc8h" is pending
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-j4ccr		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-j4ccr" is pending

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

... skipping 10 lines ...
Node	ip-172-20-58-182.ap-northeast-1.compute.internal	node "ip-172-20-58-182.ap-northeast-1.compute.internal" of role "node" is not ready
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-znc8h				system-node-critical pod "calico-node-znc8h" is pending
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-j4ccr		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-j4ccr" is pending

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

... skipping 14 lines ...
Pod	kube-system/calico-node-r27cq				system-node-critical pod "calico-node-r27cq" is pending
Pod	kube-system/calico-node-rhl59				system-node-critical pod "calico-node-rhl59" is pending
Pod	kube-system/calico-node-xhm4s				system-node-critical pod "calico-node-xhm4s" is pending
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 11 lines ...
Pod	kube-system/calico-node-r27cq				system-node-critical pod "calico-node-r27cq" is pending
Pod	kube-system/calico-node-rhl59				system-node-critical pod "calico-node-rhl59" is pending
Pod	kube-system/calico-node-xhm4s				system-node-critical pod "calico-node-xhm4s" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 9 lines ...
KIND	NAME									MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr			system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck					system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj					system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-57-242.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-242.ap-northeast-1.compute.internal" is pending

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

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

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-5f6cfd688c-hc8gr	system-cluster-critical pod "calico-kube-controllers-5f6cfd688c-hc8gr" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-nlpck			system-cluster-critical pod "coredns-64497985bd-nlpck" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-x9vlj			system-cluster-critical pod "coredns-64497985bd-x9vlj" is not ready (coredns)

Validation Failed
W0914 08:57:18.306446    4152 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0914 08:57:28.312597    4093 dumplogs.go:38] /logs/artifacts/4cd74601-1537-11ec-840b-fe625b2855d5/kops toolbox dump --name e2e-7230299cf8-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0914 08:57:28.328671    4163 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0914 08:57:28.328832    4163 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/14 08:57:40 Dumping node ip-172-20-40-153.ap-northeast-1.compute.internal
2021/09/14 08:57:45 Dumping node ip-172-20-41-21.ap-northeast-1.compute.internal
2021/09/14 08:57:50 Dumping node ip-172-20-44-195.ap-northeast-1.compute.internal
... skipping 1231 lines ...
route-table:rtb-0ca2697823241a268	ok
vpc:vpc-035df5690fd7041ad	ok
dhcp-options:dopt-0207f36f5a60e03f0	ok
Deleted kubectl config for e2e-7230299cf8-ec357.test-cncf-aws.k8s.io

Deleted cluster: "e2e-7230299cf8-ec357.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace