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

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0909 02:17:54.811610    4067 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0909 02:17:54.813584    4067 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.2+v1.22.0-beta.1-38-g85f98ed240/linux/amd64/kops
I0909 02:17:55.753503    4067 up.go:43] Cleaning up any leaked resources from previous cluster
I0909 02:17:55.753548    4067 dumplogs.go:38] /logs/artifacts/e88406bf-1113-11ec-bf73-ae50abde5ff3/kops toolbox dump --name e2e-736c543c14-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0909 02:17:55.783808    4086 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0909 02:17:55.783933    4086 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-736c543c14-7012d.test-cncf-aws.k8s.io" not found
W0909 02:17:56.343817    4067 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0909 02:17:56.343887    4067 down.go:48] /logs/artifacts/e88406bf-1113-11ec-bf73-ae50abde5ff3/kops delete cluster --name e2e-736c543c14-7012d.test-cncf-aws.k8s.io --yes
I0909 02:17:56.373476    4096 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0909 02:17:56.373639    4096 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-736c543c14-7012d.test-cncf-aws.k8s.io" not found
I0909 02:17:56.878617    4067 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/09 02:17:56 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
I0909 02:17:56.888496    4067 http.go:37] curl https://ip.jsb.workers.dev
I0909 02:17:57.087293    4067 up.go:144] /logs/artifacts/e88406bf-1113-11ec-bf73-ae50abde5ff3/kops create cluster --name e2e-736c543c14-7012d.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.4 --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.202.198.26/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I0909 02:17:57.114578    4106 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0909 02:17:57.114710    4106 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0909 02:17:57.168198    4106 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0909 02:17:57.704865    4106 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0909 02:18:27.409843    4067 up.go:181] /logs/artifacts/e88406bf-1113-11ec-bf73-ae50abde5ff3/kops validate cluster --name e2e-736c543c14-7012d.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0909 02:18:27.437477    4126 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0909 02:18:27.438325    4126 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-736c543c14-7012d.test-cncf-aws.k8s.io

W0909 02:18:29.114130    4126 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-736c543c14-7012d.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
W0909 02:18:39.146694    4126 validate_cluster.go:232] (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
W0909 02:18:49.181937    4126 validate_cluster.go:232] (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
W0909 02:18:59.213251    4126 validate_cluster.go:232] (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
W0909 02:19:09.249505    4126 validate_cluster.go:232] (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
W0909 02:19:19.313537    4126 validate_cluster.go:232] (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
W0909 02:19:29.371893    4126 validate_cluster.go:232] (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
W0909 02:19:39.404740    4126 validate_cluster.go:232] (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
W0909 02:19:49.436459    4126 validate_cluster.go:232] (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
W0909 02:19:59.473833    4126 validate_cluster.go:232] (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
W0909 02:20:09.508555    4126 validate_cluster.go:232] (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
W0909 02:20:19.572821    4126 validate_cluster.go:232] (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
W0909 02:20:29.615073    4126 validate_cluster.go:232] (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
W0909 02:20:39.644849    4126 validate_cluster.go:232] (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
W0909 02:20:49.761695    4126 validate_cluster.go:232] (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
W0909 02:20:59.806411    4126 validate_cluster.go:232] (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
W0909 02:21:09.851168    4126 validate_cluster.go:232] (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
W0909 02:21:19.888192    4126 validate_cluster.go:232] (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
W0909 02:21:29.929605    4126 validate_cluster.go:232] (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
W0909 02:21:39.978252    4126 validate_cluster.go:232] (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
W0909 02:21:50.065278    4126 validate_cluster.go:232] (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
W0909 02:22:00.103595    4126 validate_cluster.go:232] (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
W0909 02:22:10.137389    4126 validate_cluster.go:232] (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
W0909 02:22:20.176510    4126 validate_cluster.go:232] (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
W0909 02:22:30.214062    4126 validate_cluster.go:232] (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
W0909 02:22:40.317117    4126 validate_cluster.go:232] (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
W0909 02:22:50.351433    4126 validate_cluster.go:232] (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
W0909 02:23:00.390372    4126 validate_cluster.go:232] (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
W0909 02:23:10.434698    4126 validate_cluster.go:232] (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
W0909 02:23:20.481128    4126 validate_cluster.go:232] (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
W0909 02:23:30.564327    4126 validate_cluster.go:232] (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
W0909 02:23:40.594295    4126 validate_cluster.go:232] (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
W0909 02:23:50.628195    4126 validate_cluster.go:232] (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
W0909 02:24:00.700695    4126 validate_cluster.go:232] (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
W0909 02:24:10.738715    4126 validate_cluster.go:232] (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
W0909 02:24:20.847668    4126 validate_cluster.go:232] (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
W0909 02:24:30.936980    4126 validate_cluster.go:232] (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
W0909 02:24:41.006695    4126 validate_cluster.go:232] (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
W0909 02:24:51.040964    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:25:05.955538    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:25:19.305680    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:25:32.533023    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:25:45.974351    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:25:59.051758    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:26:12.512487    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:26:25.812163    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:26:38.858249    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:26:51.949681    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:27:05.119867    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:27:18.196596    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:27:31.299680    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:27:44.515678    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:27:57.623716    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:28:10.743605    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:28:23.897898    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:28:36.896259    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:28:49.971579    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:29:03.827887    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:29:16.958365    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:29:30.079414    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:29:43.145983    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:29:56.572218    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:30:09.726156    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:30:22.915302    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:30:36.063551    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:30:49.224464    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:31:02.440246    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:31:15.544622    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:31:28.679069    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:31:41.795950    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:31:54.987190    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:32:08.272277    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:32:21.467512    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:32:34.668698    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:32:47.745818    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:33:01.642435    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:33:14.722455    4126 validate_cluster.go:232] (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-0ea80453b1ee1cd49				machine "i-0ea80453b1ee1cd49" has not yet joined cluster
Node	ip-172-20-59-41.ap-southeast-1.compute.internal	node "ip-172-20-59-41.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-lvrsh			system-node-critical pod "cilium-lvrsh" is pending
Pod	kube-system/coredns-5dc785954d-bvbn6		system-cluster-critical pod "coredns-5dc785954d-bvbn6" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-fw6jc	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-fw6jc" is pending

Validation Failed
W0909 02:33:27.863024    4126 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0909 02:33:37.868800    4067 dumplogs.go:38] /logs/artifacts/e88406bf-1113-11ec-bf73-ae50abde5ff3/kops toolbox dump --name e2e-736c543c14-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0909 02:33:37.885489    4138 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0909 02:33:37.885611    4138 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/09 02:33:51 Dumping node ip-172-20-59-41.ap-southeast-1.compute.internal
2021/09/09 02:34:01 dumping node not registered in kubernetes: 54.254.7.138
2021/09/09 02:34:01 Dumping node 54.254.7.138
... skipping 1282 lines ...
route-table:rtb-0da1962ea616cc8e5	ok
vpc:vpc-06375b8cf06b264dc	ok
dhcp-options:dopt-0b85e50ba3f155f39	ok
Deleted kubectl config for e2e-736c543c14-7012d.test-cncf-aws.k8s.io

Deleted cluster: "e2e-736c543c14-7012d.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace