This job view page is being replaced by Spyglass soon. Check out the new job view.
PRolemarkus: Enable IRSA for CCM
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-06-24 13:01
Elapsed24m33s
Revision362ace21dbeae54d65bdc561573e0a44b40621c0
Refs 11818

No Test Failures!


Error lines from build-log.txt

... skipping 483 lines ...
I0624 13:05:36.084453    4244 up.go:43] Cleaning up any leaked resources from previous cluster
I0624 13:05:36.084495    4244 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0624 13:05:36.101127   11793 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 13:05:36.102042   11793 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io" not found
W0624 13:05:36.629929    4244 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0624 13:05:36.629999    4244 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --yes
I0624 13:05:36.649838   11804 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 13:05:36.649927   11804 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io" not found
I0624 13:05:37.106663    4244 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/06/24 13:05:37 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
I0624 13:05:37.115020    4244 http.go:37] curl https://ip.jsb.workers.dev
I0624 13:05:37.226534    4244 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.0-beta.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210621 --channel=alpha --networking=kubenet --container-runtime=containerd --override=cluster.spec.cloudControllerManager.cloudProvider=aws --admin-access 34.71.197.89/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0624 13:05:37.242573   11814 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 13:05:37.243017   11814 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0624 13:05:37.289451   11814 create_cluster.go:739] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0624 13:05:37.857750   11814 new_cluster.go:1054]  Cloud Provider ID = aws
... skipping 31 lines ...

I0624 13:06:07.788405    4244 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0624 13:06:07.806070   11836 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 13:06:07.806182   11836 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

W0624 13:06:09.480757   11836 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-cbaca3167c-2049b.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
W0624 13:06:19.552655   11836 validate_cluster.go:221] (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
W0624 13:06:29.597267   11836 validate_cluster.go:221] (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
W0624 13:06:39.626949   11836 validate_cluster.go:221] (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
W0624 13:06:49.683402   11836 validate_cluster.go:221] (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
W0624 13:06:59.720658   11836 validate_cluster.go:221] (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
W0624 13:07:09.756563   11836 validate_cluster.go:221] (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
W0624 13:07:19.792344   11836 validate_cluster.go:221] (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
W0624 13:07:29.830806   11836 validate_cluster.go:221] (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
W0624 13:07:39.886278   11836 validate_cluster.go:221] (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
W0624 13:07:49.934507   11836 validate_cluster.go:221] (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
W0624 13:07:59.970747   11836 validate_cluster.go:221] (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
W0624 13:08:10.002073   11836 validate_cluster.go:221] (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
W0624 13:08:20.035813   11836 validate_cluster.go:221] (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
W0624 13:08:30.075021   11836 validate_cluster.go:221] (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
W0624 13:08:40.123787   11836 validate_cluster.go:221] (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
W0624 13:08:50.168615   11836 validate_cluster.go:221] (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
W0624 13:09:00.199954   11836 validate_cluster.go:221] (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
W0624 13:09:10.229305   11836 validate_cluster.go:221] (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
W0624 13:09:20.264903   11836 validate_cluster.go:221] (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
W0624 13:09:30.294324   11836 validate_cluster.go:221] (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
W0624 13:09:40.339737   11836 validate_cluster.go:221] (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
W0624 13:09:50.374004   11836 validate_cluster.go:221] (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
W0624 13:10:00.425095   11836 validate_cluster.go:221] (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 16 lines ...
Pod	kube-system/ebs-csi-node-7x8f2						system-node-critical pod "ebs-csi-node-7x8f2" is pending
Pod	kube-system/ebs-csi-node-fs7d7						system-node-critical pod "ebs-csi-node-fs7d7" is pending
Pod	kube-system/ebs-csi-node-rb7nv						system-node-critical pod "ebs-csi-node-rb7nv" is pending
Pod	kube-system/ebs-csi-node-sphpp						system-node-critical pod "ebs-csi-node-sphpp" is pending
Pod	kube-system/kube-proxy-ip-172-20-52-161.ap-southeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-161.ap-southeast-2.compute.internal" is pending

Validation Failed
W0624 13:10:14.790930   11836 validate_cluster.go:221] (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 13 lines ...
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending
Pod	kube-system/ebs-csi-node-7x8f2				system-node-critical pod "ebs-csi-node-7x8f2" is pending

Validation Failed
W0624 13:10:27.846728   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:10:40.969155   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:10:54.133206   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:11:07.261605   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:11:20.546016   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:11:33.626921   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:11:46.725074   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:11:59.805319   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:12:12.984975   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:12:26.065674   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:12:39.135546   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:12:52.179685   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:13:05.321107   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:13:18.406088   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:13:31.464041   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:13:44.556566   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:13:57.609786   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:14:11.296107   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:14:24.457078   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:14:37.583403   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:14:50.727200   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:15:03.936064   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:15:17.118634   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:15:30.143505   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:15:43.259599   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:15:56.352592   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:16:09.486252   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:16:22.529089   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:16:35.593858   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:16:48.799469   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:17:02.091521   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:17:15.123581   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:17:28.343989   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:17:41.553790   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:17:54.715859   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:18:08.493225   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:18:21.573228   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:18:34.696312   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:18:47.887118   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:19:00.997652   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:19:14.121244   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:19:27.239470   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:19:40.352482   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:19:53.476707   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:20:06.713673   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:20:19.843136   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:20:33.009893   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:20:47.674061   11836 validate_cluster.go:221] (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 12 lines ...
Node	ip-172-20-52-161.ap-southeast-2.compute.internal	node "ip-172-20-52-161.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-111.ap-southeast-2.compute.internal	node "ip-172-20-54-111.ap-southeast-2.compute.internal" of role "master" is not ready
Node	ip-172-20-62-141.ap-southeast-2.compute.internal	node "ip-172-20-62-141.ap-southeast-2.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-fd5gc		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-fd5gc" is pending
Pod	kube-system/coredns-f45c4bf76-q5ppd			system-cluster-critical pod "coredns-f45c4bf76-q5ppd" is pending

Validation Failed
W0624 13:21:00.811574   11836 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0624 13:21:10.818753    4244 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0624 13:21:10.835795   11848 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0624 13:21:10.835971   11848 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/06/24 13:21:24 Dumping node ip-172-20-38-155.ap-southeast-2.compute.internal
2021/06/24 13:21:31 Dumping node ip-172-20-46-29.ap-southeast-2.compute.internal
2021/06/24 13:21:38 Dumping node ip-172-20-52-161.ap-southeast-2.compute.internal
... skipping 1432 lines ...
route-table:rtb-04766fc091cd0cd4b	ok
vpc:vpc-0e5fd7794ed1e1629	ok
dhcp-options:dopt-0dca3e8c6b2f5605b	ok
Deleted kubectl config for e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

Deleted cluster: "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...