This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-16 03:52
Elapsed18m53s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0916 03:53:21.464004    4108 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0916 03:53:21.465569    4108 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-138-gd9f21f94af/linux/amd64/kops
I0916 03:53:22.197579    4108 up.go:43] Cleaning up any leaked resources from previous cluster
I0916 03:53:22.197622    4108 dumplogs.go:38] /logs/artifacts/7340b14e-16a1-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-025f565616-cfa81.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0916 03:53:22.216302    4127 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 03:53:22.216431    4127 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-025f565616-cfa81.test-cncf-aws.k8s.io" not found
W0916 03:53:22.748991    4108 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0916 03:53:22.749071    4108 down.go:48] /logs/artifacts/7340b14e-16a1-11ec-a0c8-aafcb65c973d/kops delete cluster --name e2e-025f565616-cfa81.test-cncf-aws.k8s.io --yes
I0916 03:53:22.767580    4136 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 03:53:22.767704    4136 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-025f565616-cfa81.test-cncf-aws.k8s.io" not found
I0916 03:53:23.219573    4108 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/16 03:53:23 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
I0916 03:53:23.231356    4108 http.go:37] curl https://ip.jsb.workers.dev
I0916 03:53:23.321774    4108 up.go:144] /logs/artifacts/7340b14e-16a1-11ec-a0c8-aafcb65c973d/kops create cluster --name e2e-025f565616-cfa81.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 104.197.67.250/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0916 03:53:23.343121    4146 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 03:53:23.343231    4146 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 03:53:23.368632    4146 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0916 03:53:23.867867    4146 new_cluster.go:1052]  Cloud Provider ID = aws
... skipping 45 lines ...

I0916 03:53:43.647687    4108 up.go:181] /logs/artifacts/7340b14e-16a1-11ec-a0c8-aafcb65c973d/kops validate cluster --name e2e-025f565616-cfa81.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0916 03:53:43.669278    4165 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 03:53:43.670657    4165 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-025f565616-cfa81.test-cncf-aws.k8s.io

W0916 03:53:45.270863    4165 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-025f565616-cfa81.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
W0916 03:53:55.303308    4165 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
W0916 03:54:05.338386    4165 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
W0916 03:54:15.372355    4165 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
W0916 03:54:25.441504    4165 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
W0916 03:54:35.474984    4165 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
W0916 03:54:45.508032    4165 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
W0916 03:54:55.541929    4165 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
W0916 03:55:05.585063    4165 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
W0916 03:55:15.616677    4165 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
W0916 03:55:25.666513    4165 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
W0916 03:55:35.704359    4165 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
W0916 03:55:45.753508    4165 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
W0916 03:55:55.783481    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 03:56:05.804794    4165 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-025f565616-cfa81.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
W0916 03:56:15.841573    4165 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
W0916 03:56:25.906871    4165 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
W0916 03:56:35.973834    4165 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
W0916 03:56:46.005680    4165 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
W0916 03:56:56.041138    4165 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
W0916 03:57:06.092192    4165 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
W0916 03:57:16.129660    4165 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
W0916 03:57:26.165157    4165 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
W0916 03:57:36.271062    4165 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
W0916 03:57:46.306435    4165 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
W0916 03:57:56.340667    4165 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
W0916 03:58:06.382245    4165 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
W0916 03:58:16.452691    4165 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
W0916 03:58:26.520504    4165 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
W0916 03:58:36.583185    4165 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
W0916 03:58:46.616160    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 03:59:00.822980    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 03:59:13.398974    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 03:59:26.089667    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 03:59:38.732099    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 03:59:51.447171    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:00:04.099513    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:00:16.848347    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:00:29.631572    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:00:42.393583    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:00:55.011973    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:01:07.852562    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:01:20.504115    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:01:33.216611    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:01:45.976868    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:01:58.618781    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:02:11.281497    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:02:23.944520    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:02:36.560137    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:02:49.161617    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:03:02.441094    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:03:15.098371    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:03:27.740028    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:03:40.354332    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:03:53.381687    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:05:09.530632    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:05:22.132231    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:05:34.809898    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:05:47.499079    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:06:00.167849    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:06:13.179448    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:06:25.867253    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:06:38.618925    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:06:51.326278    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:07:04.420835    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:07:17.318205    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:07:29.861908    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:07:42.734659    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:07:55.612051    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

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

... skipping 9 lines ...
Machine	i-0e37f0fd3dbf9edeb					machine "i-0e37f0fd3dbf9edeb" has not yet joined cluster
Node	ip-172-20-36-114.ap-northeast-2.compute.internal	node "ip-172-20-36-114.ap-northeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-s6k7x				system-node-critical pod "cilium-s6k7x" is pending
Pod	kube-system/coredns-5dc785954d-vw2tf			system-cluster-critical pod "coredns-5dc785954d-vw2tf" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-8qdvj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-8qdvj" is pending

Validation Failed
W0916 04:08:46.482069    4165 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0916 04:08:56.491898    4108 dumplogs.go:38] /logs/artifacts/7340b14e-16a1-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-025f565616-cfa81.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0916 04:08:56.511992    4175 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 04:08:56.512943    4175 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/16 04:09:08 Dumping node ip-172-20-36-114.ap-northeast-2.compute.internal
2021/09/16 04:09:18 dumping node not registered in kubernetes: 13.209.16.168
2021/09/16 04:09:18 Dumping node 13.209.16.168
... skipping 1255 lines ...
route-table:rtb-0df59fa2b643e9d06	ok
vpc:vpc-05b66239e90c6675b	ok
dhcp-options:dopt-04fbf7d9d44363736	ok
Deleted kubectl config for e2e-025f565616-cfa81.test-cncf-aws.k8s.io

Deleted cluster: "e2e-025f565616-cfa81.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace