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

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0916 02:17:31.061878    4062 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0916 02:17:31.063568    4062 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.2+v1.22.0-beta.1-62-gbf2982413f/linux/amd64/kops
I0916 02:17:32.014586    4062 up.go:43] Cleaning up any leaked resources from previous cluster
I0916 02:17:32.014727    4062 dumplogs.go:38] /logs/artifacts/0a147d48-1694-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0916 02:17:32.031354    4081 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 02:17:32.031542    4081 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io" not found
W0916 02:17:32.522352    4062 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0916 02:17:32.522391    4062 down.go:48] /logs/artifacts/0a147d48-1694-11ec-a0c8-aafcb65c973d/kops delete cluster --name e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io --yes
I0916 02:17:32.539964    4091 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 02:17:32.540059    4091 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io" not found
I0916 02:17:32.997508    4062 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/16 02:17:33 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0916 02:17:33.005896    4062 http.go:37] curl https://ip.jsb.workers.dev
I0916 02:17:33.215682    4062 up.go:144] /logs/artifacts/0a147d48-1694-11ec-a0c8-aafcb65c973d/kops create cluster --name e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.132.118.163/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0916 02:17:33.231180    4102 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 02:17:33.231303    4102 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0916 02:17:33.254939    4102 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0916 02:17:33.738690    4102 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0916 02:18:03.056255    4062 up.go:181] /logs/artifacts/0a147d48-1694-11ec-a0c8-aafcb65c973d/kops validate cluster --name e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0916 02:18:03.073792    4121 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 02:18:03.074514    4121 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io

W0916 02:18:04.701804    4121 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 02:18:14.746272    4121 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b2924e1e8d-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-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0916 02:18:34.861808    4121 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 02:18:44.905035    4121 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b2924e1e8d-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-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0916 02:19:15.013197    4121 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 02:19:25.043395    4121 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b2924e1e8d-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-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0916 02:20:25.595240    4121 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 02:20:35.705593    4121 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b2924e1e8d-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-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0916 02:22:06.271759    4121 validate_cluster.go:232] (will retry): cluster not yet healthy
W0916 02:22:16.292896    4121 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b2924e1e8d-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-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

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

... skipping 9 lines ...
Machine	i-07b01fb2e0e688572					machine "i-07b01fb2e0e688572" has not yet joined cluster
Node	ip-172-20-43-149.ap-southeast-2.compute.internal	node "ip-172-20-43-149.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-dx9ng				system-node-critical pod "cilium-dx9ng" is pending
Pod	kube-system/coredns-5dc785954d-snbdw			system-cluster-critical pod "coredns-5dc785954d-snbdw" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h45gx		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h45gx" is pending

Validation Failed
W0916 02:32:56.468941    4121 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0916 02:33:06.475789    4062 dumplogs.go:38] /logs/artifacts/0a147d48-1694-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0916 02:33:06.494916    4131 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0916 02:33:06.495000    4131 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/16 02:33:19 Dumping node ip-172-20-43-149.ap-southeast-2.compute.internal
2021/09/16 02:33:29 dumping node not registered in kubernetes: 13.55.202.246
2021/09/16 02:33:29 Dumping node 13.55.202.246
... skipping 1211 lines ...
route-table:rtb-07ac8ea473d6f57cb	ok
vpc:vpc-013d495ec55542b2e	ok
dhcp-options:dopt-0667ef48e9da6b595	ok
Deleted kubectl config for e2e-b2924e1e8d-7012d.test-cncf-aws.k8s.io

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