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

No Test Failures!


Error lines from build-log.txt

... skipping 132 lines ...
I1005 08:40:56.224694    4736 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I1005 08:40:56.226253    4736 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.3+v1.22.0-beta.2-13-g4aaaef677b/linux/amd64/kops
I1005 08:40:57.211833    4736 up.go:43] Cleaning up any leaked resources from previous cluster
I1005 08:40:57.211871    4736 dumplogs.go:40] /logs/artifacts/c737edf0-25b7-11ec-b80b-66e31101aeea/kops toolbox dump --name e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1005 08:40:57.227672    4756 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1005 08:40:57.227762    4756 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io" not found
W1005 08:40:57.715615    4736 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1005 08:40:57.715677    4736 down.go:48] /logs/artifacts/c737edf0-25b7-11ec-b80b-66e31101aeea/kops delete cluster --name e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io --yes
I1005 08:40:57.732326    4766 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1005 08:40:57.732431    4766 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io" not found
I1005 08:40:58.229480    4736 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/05 08:40:58 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 08:40:58.236246    4736 http.go:37] curl https://ip.jsb.workers.dev
I1005 08:40:58.322681    4736 up.go:144] /logs/artifacts/c737edf0-25b7-11ec-b80b-66e31101aeea/kops create cluster --name e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=docker --admin-access 34.69.229.196/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I1005 08:40:58.339822    4776 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1005 08:40:58.339912    4776 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1005 08:40:58.361352    4776 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1005 08:40:58.981872    4776 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 41 lines ...

I1005 08:41:26.720992    4736 up.go:181] /logs/artifacts/c737edf0-25b7-11ec-b80b-66e31101aeea/kops validate cluster --name e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1005 08:41:26.738938    4796 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1005 08:41:26.739031    4796 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io

W1005 08:41:28.192398    4796 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-6fc1d554fa-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-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 08:41:38.221630    4796 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1005 08:45:49.097100    4796 validate_cluster.go:232] (will retry): cluster not yet healthy
W1005 08:46:29.138788    4796 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

NODE STATUS
... skipping 12 lines ...
Pod	kube-system/calico-node-hhmwj				system-node-critical pod "calico-node-hhmwj" is not ready (calico-node)
Pod	kube-system/calico-node-qbbs5				system-node-critical pod "calico-node-qbbs5" is not ready (calico-node)
Pod	kube-system/calico-node-z94w4				system-node-critical pod "calico-node-z94w4" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-2jdz5			system-cluster-critical pod "coredns-64497985bd-2jdz5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bw6cp		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bw6cp" is pending

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

... skipping 11 lines ...
Pod	kube-system/calico-node-fvj5q						system-node-critical pod "calico-node-fvj5q" is not ready (calico-node)
Pod	kube-system/calico-node-hhmwj						system-node-critical pod "calico-node-hhmwj" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-2jdz5					system-cluster-critical pod "coredns-64497985bd-2jdz5" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bw6cp				system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bw6cp" is pending
Pod	kube-system/kube-proxy-ip-172-20-39-19.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-39-19.ap-northeast-2.compute.internal" is pending

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

... skipping 10 lines ...
Pod	kube-system/calico-kube-controllers-855445d444-cdmpm			system-cluster-critical pod "calico-kube-controllers-855445d444-cdmpm" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-hhmwj						system-node-critical pod "calico-node-hhmwj" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-2jdz5					system-cluster-critical pod "coredns-64497985bd-2jdz5" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-tvrkq					system-cluster-critical pod "coredns-64497985bd-tvrkq" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-56-242.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-56-242.ap-northeast-2.compute.internal" is pending

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Validation Failed
W1005 08:56:29.145754    4796 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I1005 08:56:39.151364    4736 dumplogs.go:40] /logs/artifacts/c737edf0-25b7-11ec-b80b-66e31101aeea/kops toolbox dump --name e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1005 08:56:39.169846    4807 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1005 08:56:39.169950    4807 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/10/05 08:56:51 Dumping node ip-172-20-39-19.ap-northeast-2.compute.internal
2021/10/05 08:56:58 Dumping node ip-172-20-39-197.ap-northeast-2.compute.internal
2021/10/05 08:57:06 Dumping node ip-172-20-40-67.ap-northeast-2.compute.internal
... skipping 1187 lines ...
route-table:rtb-02678cfe3a0d2b114	ok
vpc:vpc-01e6a9f015c86786e	ok
dhcp-options:dopt-0a02e62556eb1f651	ok
Deleted kubectl config for e2e-6fc1d554fa-ec357.test-cncf-aws.k8s.io

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