This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-14 12:02
Elapsed18m18s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 130 lines ...
I1014 12:03:42.224702    4743 up.go:43] Cleaning up any leaked resources from previous cluster
I1014 12:03:42.224734    4743 dumplogs.go:40] /logs/artifacts/98588d42-2ce6-11ec-87ab-3252014cf394/kops toolbox dump --name e2e-3556ffee54-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1014 12:03:42.242093    4764 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1014 12:03:42.242182    4764 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-3556ffee54-773a8.test-cncf-aws.k8s.io" not found
W1014 12:03:42.771415    4743 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1014 12:03:42.771468    4743 down.go:48] /logs/artifacts/98588d42-2ce6-11ec-87ab-3252014cf394/kops delete cluster --name e2e-3556ffee54-773a8.test-cncf-aws.k8s.io --yes
I1014 12:03:42.787511    4774 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1014 12:03:42.788216    4774 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-3556ffee54-773a8.test-cncf-aws.k8s.io" not found
I1014 12:03:43.276008    4743 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/14 12:03:43 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
I1014 12:03:43.285353    4743 http.go:37] curl https://ip.jsb.workers.dev
I1014 12:03:43.372567    4743 up.go:144] /logs/artifacts/98588d42-2ce6-11ec-87ab-3252014cf394/kops create cluster --name e2e-3556ffee54-773a8.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.66.24.217/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I1014 12:03:43.387106    4785 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1014 12:03:43.387178    4785 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1014 12:03:43.435187    4785 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1014 12:03:44.017615    4785 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 45 lines ...

I1014 12:04:02.288794    4743 up.go:181] /logs/artifacts/98588d42-2ce6-11ec-87ab-3252014cf394/kops validate cluster --name e2e-3556ffee54-773a8.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1014 12:04:02.303569    4805 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1014 12:04:02.303658    4805 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-3556ffee54-773a8.test-cncf-aws.k8s.io

W1014 12:04:03.948138    4805 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-3556ffee54-773a8.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
W1014 12:04:13.992068    4805 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
W1014 12:04:24.021733    4805 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
W1014 12:04:34.069646    4805 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
W1014 12:04:44.102384    4805 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
W1014 12:04:54.131511    4805 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
W1014 12:05:04.162015    4805 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
W1014 12:05:14.191416    4805 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
W1014 12:05:24.221331    4805 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
W1014 12:05:34.264075    4805 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
W1014 12:05:44.295380    4805 validate_cluster.go:221] (will retry): cluster not yet healthy
W1014 12:05:54.325620    4805 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-3556ffee54-773a8.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
W1014 12:06:04.368029    4805 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
W1014 12:06:14.399873    4805 validate_cluster.go:221] (will retry): cluster not yet healthy
W1014 12:06:24.427679    4805 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-3556ffee54-773a8.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
W1014 12:06:34.454852    4805 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
W1014 12:06:44.484761    4805 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
W1014 12:06:54.517519    4805 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
W1014 12:07:04.550434    4805 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
W1014 12:07:14.580572    4805 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
W1014 12:07:24.610050    4805 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
W1014 12:07:34.638039    4805 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
W1014 12:07:44.667555    4805 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
W1014 12:07:54.698690    4805 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
W1014 12:08:04.732603    4805 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
W1014 12:08:14.777272    4805 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
W1014 12:08:24.807413    4805 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
W1014 12:08:34.838602    4805 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
W1014 12:08:44.867653    4805 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
W1014 12:08:54.903461    4805 validate_cluster.go:221] (will retry): cluster not yet healthy
W1014 12:09:34.933422    4805 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-3556ffee54-773a8.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
... skipping 8 lines ...
Machine	i-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:09:49.853762    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:10:02.985697    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:10:16.417747    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:10:29.908175    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:10:43.060186    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:10:56.590145    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:11:10.018588    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:11:23.319653    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:11:36.519969    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:11:49.769488    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:12:02.919702    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:12:16.133181    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:12:29.543573    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:12:42.998986    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:12:56.362865    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:13:09.588245    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:13:22.633776    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:13:36.017847    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:13:49.837159    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:14:03.007942    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:14:16.287258    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:14:29.660532    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:14:42.817750    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:14:56.217961    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:15:09.521196    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:15:23.367010    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:15:36.658462    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:15:49.887439    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:16:03.199221    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:16:16.322346    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:16:29.480553    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:16:42.885285    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:16:56.255033    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:17:09.675825    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:17:22.839751    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:17:36.104800    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:17:50.031944    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:18:03.472088    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:18:16.936941    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:18:30.375629    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:18:43.766270    4805 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-0f8d7d4b6ef5bc180					machine "i-0f8d7d4b6ef5bc180" has not yet joined cluster
Node	ip-172-20-53-247.ap-southeast-1.compute.internal	node "ip-172-20-53-247.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-vqscr				system-node-critical pod "cilium-vqscr" is pending
Pod	kube-system/coredns-64497985bd-hw2z2			system-cluster-critical pod "coredns-64497985bd-hw2z2" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-zd4d9		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-zd4d9" is pending

Validation Failed
W1014 12:18:56.936020    4805 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1014 12:19:06.944834    4743 dumplogs.go:40] /logs/artifacts/98588d42-2ce6-11ec-87ab-3252014cf394/kops toolbox dump --name e2e-3556ffee54-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1014 12:19:06.963089    4815 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1014 12:19:06.963213    4815 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/14 12:19:20 Dumping node ip-172-20-53-247.ap-southeast-1.compute.internal
2021/10/14 12:19:30 dumping node not registered in kubernetes: 13.212.138.226
2021/10/14 12:19:30 Dumping node 13.212.138.226
... skipping 1165 lines ...
route-table:rtb-01d6deb5a046a817e	ok
vpc:vpc-0fb82f65f11f98f77	ok
dhcp-options:dopt-05bbf15a8b9b23201	ok
Deleted kubectl config for e2e-3556ffee54-773a8.test-cncf-aws.k8s.io

Deleted cluster: "e2e-3556ffee54-773a8.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace