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

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1003 09:25:19.353456    4728 up.go:43] Cleaning up any leaked resources from previous cluster
I1003 09:25:19.353490    4728 dumplogs.go:40] /logs/artifacts/a4063970-242b-11ec-b766-fab168edef1d/kops toolbox dump --name e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1003 09:25:19.369953    4748 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1003 09:25:19.370077    4748 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io" not found
W1003 09:25:19.883957    4728 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1003 09:25:19.884033    4728 down.go:48] /logs/artifacts/a4063970-242b-11ec-b766-fab168edef1d/kops delete cluster --name e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io --yes
I1003 09:25:19.899962    4758 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1003 09:25:19.900058    4758 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io" not found
I1003 09:25:20.426940    4728 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/03 09:25:20 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
I1003 09:25:20.435324    4728 http.go:37] curl https://ip.jsb.workers.dev
I1003 09:25:20.519955    4728 up.go:144] /logs/artifacts/a4063970-242b-11ec-b766-fab168edef1d/kops create cluster --name e2e-a3aa0f26cb-53349.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 35.192.90.167/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I1003 09:25:20.534789    4769 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1003 09:25:20.534867    4769 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1003 09:25:20.577063    4769 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1003 09:25:21.078412    4769 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 46 lines ...

I1003 09:25:41.968526    4728 up.go:181] /logs/artifacts/a4063970-242b-11ec-b766-fab168edef1d/kops validate cluster --name e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1003 09:25:41.984576    4790 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1003 09:25:41.984717    4790 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io

W1003 09:25:43.680339    4790 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:25:53.764308    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:26:03.791181    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:26:13.818187    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:26:23.848831    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:26:33.877693    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:26:43.906052    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:26:53.936901    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:27:03.968373    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:27:13.995973    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:27:24.030870    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:27:34.085506    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:27:44.149482    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:27:54.183029    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:28:04.212025    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:28:14.274664    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:28:24.351504    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:28:34.382780    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:28:44.445816    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:28:54.495528    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:29:04.524834    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:29:14.561032    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:29:24.592587    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:29:34.649039    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:29:44.678467    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:29:54.706039    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-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
W1003 09:30:04.749214    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:30:19.545944    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:30:32.841122    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:30:46.012253    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:30:59.135007    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:31:12.590125    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:31:25.672960    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:31:38.864279    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:31:52.210711    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:32:05.554784    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:32:18.896597    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:32:32.063036    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:32:45.350549    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:32:58.508176    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:33:11.893079    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:33:25.044999    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:33:38.334368    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:33:51.491989    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:34:04.724854    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:34:18.843020    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:34:32.075908    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:34:45.537553    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:34:58.710911    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:35:11.948305    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:35:25.148716    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:35:38.718480    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:35:52.113143    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:36:05.371612    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:36:18.589886    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:36:31.822450    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:36:45.073834    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:36:58.487505    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:37:12.051090    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:37:25.258134    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:37:38.577224    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:37:51.936050    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:38:05.145867    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:38:19.057807    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:38:32.565478    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:38:45.811739    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:38:58.954248    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:39:12.132228    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:39:25.240805    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:39:38.481002    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:39:52.151636    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:40:07.087739    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:40:20.240995    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:40:33.576138    4790 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-06d117590e6d6c7c2				machine "i-06d117590e6d6c7c2" has not yet joined cluster
Node	ip-172-20-46-25.ap-southeast-1.compute.internal	node "ip-172-20-46-25.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-6pq82			system-node-critical pod "cilium-6pq82" is pending
Pod	kube-system/coredns-5dc785954d-8v7wj		system-cluster-critical pod "coredns-5dc785954d-8v7wj" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lksjb	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lksjb" is pending

Validation Failed
W1003 09:40:46.850095    4790 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1003 09:40:56.859980    4728 dumplogs.go:40] /logs/artifacts/a4063970-242b-11ec-b766-fab168edef1d/kops toolbox dump --name e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1003 09:40:56.877232    4802 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1003 09:40:56.877356    4802 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/03 09:41:11 Dumping node ip-172-20-46-25.ap-southeast-1.compute.internal
2021/10/03 09:41:20 dumping node not registered in kubernetes: 54.169.176.41
2021/10/03 09:41:20 Dumping node 54.169.176.41
... skipping 1163 lines ...
route-table:rtb-0a36388dd3d74c036	ok
vpc:vpc-0f7d8d0f546119d74	ok
dhcp-options:dopt-08e406c7a991f5237	ok
Deleted kubectl config for e2e-a3aa0f26cb-53349.test-cncf-aws.k8s.io

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