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-07-05 08:51
Elapsed24m29s
Revision5e0494a267e626b2ef68757737f4a3a32052fc0d
Refs 11818

No Test Failures!


Error lines from build-log.txt

... skipping 487 lines ...
I0705 08:56:13.122673    4279 up.go:43] Cleaning up any leaked resources from previous cluster
I0705 08:56:13.122720    4279 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
I0705 08:56:13.139833   11816 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0705 08:56:13.139934   11816 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io" not found
W0705 08:56:13.641803    4279 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0705 08:56:13.641914    4279 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
I0705 08:56:13.659528   11826 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0705 08:56:13.659752   11826 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io" not found
I0705 08:56:14.167061    4279 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/07/05 08:56:14 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
I0705 08:56:14.176702    4279 http.go:37] curl https://ip.jsb.workers.dev
I0705 08:56:14.262127    4279 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 104.197.46.169/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I0705 08:56:14.279192   11837 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0705 08:56:14.279311   11837 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
I0705 08:56:14.324235   11837 create_cluster.go:739] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0705 08:56:14.803187   11837 new_cluster.go:1054]  Cloud Provider ID = aws
... skipping 31 lines ...

I0705 08:56:44.231344    4279 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
I0705 08:56:44.248675   11858 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0705 08:56:44.249424   11858 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

W0705 08:56:45.839669   11858 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-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:56:55.869252   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:57:05.899914   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:57:15.949395   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:57:25.992727   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:57:36.046100   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
W0705 08:57:46.076399   11858 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-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:57:56.108745   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:58:06.142612   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:58:16.177987   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:58:26.222850   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:58:36.249400   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:58:46.285827   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:58:56.315290   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:59:06.360888   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:59:16.393456   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:59:26.437464   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:59:36.467128   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:59:46.499444   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 08:59:56.545477   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 09:00:06.589662   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 09:00:16.623327   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 09:00:26.668455   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 09:00:36.708005   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0705 09:00:46.740603   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
Machine	i-0a9f8d87ce560b82d					machine "i-0a9f8d87ce560b82d" has not yet joined cluster
Machine	i-0e8ddc39368d8de06					machine "i-0e8ddc39368d8de06" has not yet joined cluster
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-jvkff		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jvkff" is pending
Pod	kube-system/coredns-f45c4bf76-q4gx9			system-cluster-critical pod "coredns-f45c4bf76-q4gx9" is pending

Validation Failed
W0705 09:01:01.618378   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-0e8ddc39368d8de06					machine "i-0e8ddc39368d8de06" has not yet joined cluster
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-jvkff		system-cluster-critical pod "coredns-autoscaler-6f594f4c58-jvkff" is pending
Pod	kube-system/coredns-f45c4bf76-q4gx9			system-cluster-critical pod "coredns-f45c4bf76-q4gx9" is pending
Pod	kube-system/ebs-csi-node-2sk55				system-node-critical pod "ebs-csi-node-2sk55" is pending

Validation Failed
W0705 09:01:14.742708   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 14 lines ...
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-f45c4bf76-c55xh			system-cluster-critical pod "coredns-f45c4bf76-c55xh" is pending
Pod	kube-system/coredns-f45c4bf76-q4gx9			system-cluster-critical pod "coredns-f45c4bf76-q4gx9" is pending
Pod	kube-system/ebs-csi-node-8wgsm				system-node-critical pod "ebs-csi-node-8wgsm" is pending
Pod	kube-system/ebs-csi-node-kw9js				system-node-critical pod "ebs-csi-node-kw9js" is pending

Validation Failed
W0705 09:01:27.909043   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:01:41.004942   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:01:54.095807   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 11 lines ...
Node	ip-172-20-50-194.ap-southeast-1.compute.internal			node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal				node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal				node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal			node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-proxy-ip-172-20-51-17.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-51-17.ap-southeast-1.compute.internal" is pending

Validation Failed
W0705 09:02:07.232603   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:02:20.381092   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:02:33.460032   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:02:46.508743   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:02:59.673670   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:03:12.819326   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:03:25.967486   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:03:39.172627   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:03:52.425665   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:04:05.496301   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:04:18.637358   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:04:31.758286   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:04:44.864953   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:04:58.540111   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:05:11.648982   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:05:24.884767   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:05:38.161931   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:05:51.326396   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:06:04.522232   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:06:17.732106   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:06:30.959056   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:06:44.111382   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:06:57.244448   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:07:10.507160   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:07:23.645456   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:07:36.709546   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:07:49.770574   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:08:02.903873   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:08:16.106489   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:08:29.249682   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:08:42.390447   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:08:56.196736   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:09:09.380707   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:09:22.706724   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:09:35.887917   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:09:49.108066   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:10:02.262455   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:10:15.331127   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:10:28.550122   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:10:41.791484   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:10:55.116677   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:11:08.185680   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:11:21.405716   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:11:34.664283   11858 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-43-241.ap-southeast-1.compute.internal	node "ip-172-20-43-241.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-50-194.ap-southeast-1.compute.internal	node "ip-172-20-50-194.ap-southeast-1.compute.internal" of role "master" is not ready
Node	ip-172-20-51-17.ap-southeast-1.compute.internal		node "ip-172-20-51-17.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-54-34.ap-southeast-1.compute.internal		node "ip-172-20-54-34.ap-southeast-1.compute.internal" of role "node" is not ready
Node	ip-172-20-58-226.ap-southeast-1.compute.internal	node "ip-172-20-58-226.ap-southeast-1.compute.internal" of role "node" is not ready

Validation Failed
W0705 09:11:47.863664   11858 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0705 09:11:57.873114    4279 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
I0705 09:11:57.893068   11872 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0705 09:11:57.893177   11872 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
2021/07/05 09:12:12 Dumping node ip-172-20-43-241.ap-southeast-1.compute.internal
2021/07/05 09:12:20 Dumping node ip-172-20-50-194.ap-southeast-1.compute.internal
2021/07/05 09:12:30 Dumping node ip-172-20-51-17.ap-southeast-1.compute.internal
... skipping 1404 lines ...
route-table:rtb-04025e20edf49390a	ok
vpc:vpc-031c59413283be85f	ok
dhcp-options:dopt-04388c4f9befde6c7	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 ...