This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-08-27 03:41
Elapsed18m9s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0827 03:41:52.240391    4073 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0827 03:41:52.276863    4073 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.22.0-alpha.3+v1.22.0-alpha.2-278-g9c7ccff249/linux/amd64/kops
I0827 03:41:53.309167    4073 up.go:43] Cleaning up any leaked resources from previous cluster
I0827 03:41:53.309205    4073 dumplogs.go:38] /logs/artifacts/85843647-06e8-11ec-986b-46056f45e6da/kops toolbox dump --name e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0827 03:41:53.329325    4092 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true
I0827 03:41:53.329459    4092 featureflag.go:168] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io" not found
W0827 03:41:53.795302    4073 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0827 03:41:53.795539    4073 down.go:48] /logs/artifacts/85843647-06e8-11ec-986b-46056f45e6da/kops delete cluster --name e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io --yes
I0827 03:41:53.812285    4102 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true
I0827 03:41:53.812400    4102 featureflag.go:168] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io" not found
I0827 03:41:54.280994    4073 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/08/27 03:41:54 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
I0827 03:41:54.288528    4073 http.go:37] curl https://ip.jsb.workers.dev
I0827 03:41:54.372636    4073 up.go:144] /logs/artifacts/85843647-06e8-11ec-986b-46056f45e6da/kops create cluster --name e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.14 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.3_HVM-20210209-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.188.65.11/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0827 03:41:54.390495    4112 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true
I0827 03:41:54.390587    4112 featureflag.go:168] FeatureFlag "AlphaAllowGCE"=true
I0827 03:41:54.414688    4112 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0827 03:41:55.024787    4112 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0827 03:42:22.706859    4073 up.go:181] /logs/artifacts/85843647-06e8-11ec-986b-46056f45e6da/kops validate cluster --name e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0827 03:42:22.724969    4134 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true
I0827 03:42:22.725390    4134 featureflag.go:168] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io

W0827 03:42:24.207849    4134 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0827 03:42:34.241157    4134 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.medium	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

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

... skipping 9 lines ...
Machine	i-0da44f1adae2defbd					machine "i-0da44f1adae2defbd" has not yet joined cluster
Node	ip-172-20-34-84.ap-northeast-1.compute.internal		node "ip-172-20-34-84.ap-northeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-q82dt				system-node-critical pod "cilium-q82dt" is pending
Pod	kube-system/kube-dns-696cb84c7-mfj5f			system-cluster-critical pod "kube-dns-696cb84c7-mfj5f" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-cmp2j	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-cmp2j" is pending

Validation Failed
W0827 03:57:20.834501    4134 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0827 03:57:30.841415    4073 dumplogs.go:38] /logs/artifacts/85843647-06e8-11ec-986b-46056f45e6da/kops toolbox dump --name e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0827 03:57:30.859767    4145 featureflag.go:168] FeatureFlag "SpecOverrideFlag"=true
I0827 03:57:30.859883    4145 featureflag.go:168] FeatureFlag "AlphaAllowGCE"=true
2021/08/27 03:57:42 Dumping node ip-172-20-34-84.ap-northeast-1.compute.internal
2021/08/27 03:57:48 dumping node not registered in kubernetes: 18.183.98.83
2021/08/27 03:57:48 Dumping node 18.183.98.83
... skipping 1196 lines ...
route-table:rtb-04caff04c41226b30	ok
vpc:vpc-07d1c5b150d1a8b4f	ok
dhcp-options:dopt-0a6b9f3904cc45b5c	ok
Deleted kubectl config for e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io

Deleted cluster: "e2e-8f470bc342-c99a5.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace