This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-06 19:07
Elapsed18m12s
Revision
job-versionv1.23.0-alpha.3.183+a861de6d162f61
kubetest-version
revisionv1.23.0-alpha.3.183+a861de6d162f61

Test Failures


kubetest Up 15m39s

kops validate cluster failed: error during /tmp/kops618968547/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ WRAPPED_COMMAND_PID=31
+ wait 31
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --deployment=kops --env=KOPS_ARCH=amd64 --env=KUBE_SSH_USER=ec2-user --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=ci/latest --ginkgo-parallel --kops-image=309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --kops-args=--master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --kops-overrides=spec.docker.selinuxEnabled=true --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-ssh-user=ec2-user --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.focus=\[sig-storage\].*\[Slow\] --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8' --timeout=120m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 156 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=83c3bff5569a4ae2d1c0952d1cb01c0f
sha512sum(kubernetes-test-linux-amd64.tar.gz)=a93383a48f24cd9311c54388aec2a74a7a5bba7f92b3b7d0e1c6db5142911d1d1a1fa8c556a4d5e6244c187fd3385c8b1a746b7bba93efdd84ea5ee9288b4956

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/06 19:07:40 process.go:155: Step './get-kube.sh' finished in 28.881762331s
2021/10/06 19:07:40 process.go:153: Running: /tmp/kops618968547/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
Error: cluster not found "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/06 19:07:41 process.go:155: Step '/tmp/kops618968547/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 777.601797ms
2021/10/06 19:07:41 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/06 19:07:41 kops.go:514: 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
2021/10/06 19:07:41 util.go:68: curl https://ip.jsb.workers.dev
2021/10/06 19:07:41 kops.go:439: Using external IP for admin access: 34.121.91.241/32
2021/10/06 19:07:41 process.go:153: Running: /tmp/kops618968547/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ap-southeast-2b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.183+a861de6d162f61 --admin-access 34.121.91.241/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1006 19:07:41.380151     988 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1006 19:07:41.407373     988 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1006 19:07:41.892906     988 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/06 19:08:11 process.go:155: Step '/tmp/kops618968547/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones ap-southeast-2b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.183+a861de6d162f61 --admin-access 34.121.91.241/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 29.912964394s
2021/10/06 19:08:11 process.go:153: Running: /tmp/kops618968547/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1006 19:08:11.310822    1008 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1006 19:08:12.989040    1008 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1006 19:08:23.027066    1008 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1006 19:08:33.052364    1008 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1006 19:08:43.089273    1008 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:08:53.140377    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:09:03.195089    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:09:13.245348    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:09:23.292012    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:09:33.338659    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:09:43.383119    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:09:53.415971    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:10:03.447915    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:10:13.481668    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:10:23.517031    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:10:33.551554    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:10:43.587758    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:10:53.630122    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:11:03.667731    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:11:13.712447    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:11:23.744573    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:11:33.779021    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:11:43.822413    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:11:53.864188    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:12:03.904129    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

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
W1006 19:12:13.936281    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:12:29.168441    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:12:42.448620    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:12:55.853962    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:13:08.904145    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:13:21.989643    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:13:34.970491    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:13:48.071852    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:14:01.049272    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:14:14.073264    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:14:27.169997    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:14:40.241055    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:14:53.171611    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:15:06.313263    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:15:19.499708    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:15:32.418519    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:15:45.579246    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:15:58.578932    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:16:11.605141    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:16:25.186829    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:16:38.200294    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:16:51.257990    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:17:04.411938    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:17:17.407586    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:17:30.377331    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:17:43.451672    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:17:56.476758    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:18:09.585174    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:18:22.546946    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:18:35.504203    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:18:49.203196    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

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

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

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

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

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

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

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

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

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

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:20:07.622676    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:20:21.248513    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:20:34.242647    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:20:47.336145    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:21:00.311712    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:21:13.335384    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:21:26.355382    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:21:39.344964    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:21:52.605718    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:22:05.602268    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:22:18.592616    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:22:31.617764    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:22:44.578421    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:22:57.641672    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2b	Master	c5.large	1	1	ap-southeast-2b
nodes-ap-southeast-2b	Node	t3.medium	4	4	ap-southeast-2b

... skipping 7 lines ...
Machine	i-078284422ee8ff425				machine "i-078284422ee8ff425" has not yet joined cluster
Machine	i-08c7ffed9d329f93d				machine "i-08c7ffed9d329f93d" has not yet joined cluster
Machine	i-0f3e04035be2e4bf4				machine "i-0f3e04035be2e4bf4" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-fgc7j		system-cluster-critical pod "coredns-5dc785954d-fgc7j" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-g4zl2	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-g4zl2" is pending

Validation Failed
W1006 19:23:10.721003    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/06 19:23:20 process.go:155: Step '/tmp/kops618968547/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m9.454450292s
2021/10/06 19:23:20 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/06 19:23:20 process.go:153: Running: /tmp/kops618968547/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1006 19:23:20.760762    1021 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/06 19:23:22 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 2.185770576s
2021/10/06 19:23:22 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-5dc785954d-fgc7j
... skipping 40 lines ...
2021/10/06 19:23:43 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/06 19:23:44 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/06 19:23:44 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/06 19:23:44 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/06 19:23:45 dump.go:129: dumping node not registered in kubernetes: 13.236.165.110
2021/10/06 19:23:45 dump.go:163: Dumping node 13.236.165.110
2021/10/06 19:23:46 dump.go:132: error dumping node 13.236.165.110: could not connect: unable to SSH to "13.236.165.110": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/06 19:23:46 dump.go:129: dumping node not registered in kubernetes: 3.25.118.203
2021/10/06 19:23:46 dump.go:163: Dumping node 3.25.118.203
2021/10/06 19:23:48 dump.go:132: error dumping node 3.25.118.203: could not connect: unable to SSH to "3.25.118.203": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/06 19:23:48 dump.go:129: dumping node not registered in kubernetes: 52.63.140.137
2021/10/06 19:23:48 dump.go:163: Dumping node 52.63.140.137
2021/10/06 19:23:49 dump.go:132: error dumping node 52.63.140.137: could not connect: unable to SSH to "52.63.140.137": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/06 19:23:49 dump.go:129: dumping node not registered in kubernetes: 3.26.48.75
2021/10/06 19:23:49 dump.go:163: Dumping node 3.26.48.75
2021/10/06 19:23:51 dump.go:132: error dumping node 3.26.48.75: could not connect: unable to SSH to "3.26.48.75": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/06 19:23:51 process.go:153: Running: /tmp/kops618968547/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1006 19:23:51.165464    1140 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-southeast-2b
2021/10/06 19:23:51 process.go:155: Step '/tmp/kops618968547/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 538.867338ms
2021/10/06 19:23:51 process.go:153: Running: /tmp/kops618968547/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 198 lines ...
dhcp-options:dopt-02d4da3b8663e8a9e	ok
Deleted kubectl config for e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/06 19:25:17 process.go:155: Step '/tmp/kops618968547/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m25.799615761s
2021/10/06 19:25:17 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/06 19:25:17 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops618968547/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 723, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 569, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...