This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-20 15:36
Elapsed20m51s
Revisionmaster

Test Failures


kubetest2 Up 15m56s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 159 lines ...
I0720 15:37:16.412709    5964 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0720 15:37:16.414782    5964 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-105-gea32e12ce7/linux/amd64/kops
I0720 15:37:17.027868    5964 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519
I0720 15:37:17.042961    5964 up.go:44] Cleaning up any leaked resources from previous cluster
I0720 15:37:17.043071    5964 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0720 15:37:17.043089    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0720 15:37:17.562945    5964 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0720 15:37:17.562999    5964 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops delete cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --yes
I0720 15:37:17.563011    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops delete cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --yes
I0720 15:37:17.586878    5997 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io" not found
I0720 15:37:18.054570    5964 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/20 15:37:18 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
I0720 15:37:18.105209    5964 http.go:37] curl https://ip.jsb.workers.dev
I0720 15:37:18.222898    5964 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops create cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220706 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.188.190.85/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0720 15:37:18.222941    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops create cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20220706 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 35.188.190.85/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0720 15:37:18.244582    6007 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0720 15:37:18.273946    6007 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0720 15:37:18.825945    6007 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 519 lines ...

I0720 15:38:06.544214    5964 up.go:243] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops validate cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0720 15:38:06.544285    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops validate cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0720 15:38:06.565565    6047 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io

W0720 15:38:08.184215    6047 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-u2004-k22-docker.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
W0720 15:38:18.242112    6047 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
W0720 15:38:28.307555    6047 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
W0720 15:38:38.350059    6047 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
W0720 15:38:48.389161    6047 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
W0720 15:38:58.430957    6047 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
W0720 15:39:08.471735    6047 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
W0720 15:39:18.516624    6047 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
W0720 15:39:28.559233    6047 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
W0720 15:39:38.593932    6047 validate_cluster.go:232] (will retry): cluster not yet healthy
W0720 15:39:48.630274    6047 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-u2004-k22-docker.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
W0720 15:39:58.668660    6047 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
W0720 15:40:08.713732    6047 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
W0720 15:40:18.755548    6047 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
W0720 15:40:28.790920    6047 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
W0720 15:40:38.833955    6047 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
W0720 15:40:48.878737    6047 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
W0720 15:40:58.920706    6047 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
W0720 15:41:08.958336    6047 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
W0720 15:41:19.010066    6047 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
W0720 15:41:29.046938    6047 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 10 lines ...
Node	ip-172-20-38-134.ap-southeast-2.compute.internal	node "ip-172-20-38-134.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:41:43.558759    6047 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 10 lines ...
Node	ip-172-20-38-134.ap-southeast-2.compute.internal	node "ip-172-20-38-134.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:41:56.812831    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:42:09.858582    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:42:22.998445    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:42:36.080029    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:42:49.107879    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:43:02.155225    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:43:15.163881    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:43:28.139851    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:43:41.108683    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:43:54.106649    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:44:07.127877    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:44:20.319730    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:44:33.300347    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:44:46.312967    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:44:59.337189    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:45:12.405948    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:45:25.283058    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:45:38.893887    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:45:51.902688    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:46:04.996675    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:46:18.103266    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:46:31.215753    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:46:44.201542    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:46:57.336917    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:47:10.329781    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:47:23.340067    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:47:36.364810    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:47:49.439090    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:48:02.409082    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:48:15.470935    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:48:28.570852    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:48:41.569278    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:48:54.605623    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:49:07.743631    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:49:20.783104    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:49:34.504328    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:49:47.466214    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:50:00.406719    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:50:13.395497    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:50:26.419039    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:50:39.434022    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:50:52.414740    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:51:05.400588    6047 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 12 lines ...
Node	ip-172-20-48-171.ap-southeast-2.compute.internal	node "ip-172-20-48-171.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending

Validation Failed
W0720 15:51:18.409062    6047 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 14 lines ...
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-operator-7df799bc74-2rzjv		system-cluster-critical pod "cilium-operator-7df799bc74-2rzjv" is pending
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:51:31.452857    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:51:44.564953    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:51:57.591564    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:52:10.642519    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:52:23.822724    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:52:36.972514    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:52:49.999788    6047 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 13 lines ...
Node	ip-172-20-50-203.ap-southeast-2.compute.internal	node "ip-172-20-50-203.ap-southeast-2.compute.internal" of role "node" is not ready
Node	ip-172-20-54-236.ap-southeast-2.compute.internal	node "ip-172-20-54-236.ap-southeast-2.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-5fcc7b6498-s6qp4			system-cluster-critical pod "coredns-5fcc7b6498-s6qp4" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-669km		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-669km" is pending
Pod	kube-system/ebs-csi-controller-dbfd64777-77pqm		system-cluster-critical pod "ebs-csi-controller-dbfd64777-77pqm" is pending

Validation Failed
W0720 15:53:03.143015    6047 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0720 15:53:13.151844    5964 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0720 15:53:13.151905    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0720 15:54:19.375553    5964 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops get cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
I0720 15:54:19.375597    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops get cluster --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
I0720 15:54:19.881940    5964 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops get instancegroups --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
I0720 15:54:19.881973    5964 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/92739ff9-0841-11ed-8e3d-92e2b35ae06d/kops get instancegroups --name e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io -o yaml
... skipping 297 lines ...
route-table:rtb-01da2dbda6e634748	ok
vpc:vpc-045da649a4fcf3074	ok
dhcp-options:dopt-05062ad98f11d8c55	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-cilium-u2004-k22-docker.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace