This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-20 07:18
Elapsed17m56s
Revision
job-versionv1.23.0-alpha.3.414+c6eedc74a7b4ee
kubetest-version
revisionv1.23.0-alpha.3.414+c6eedc74a7b4ee

Test Failures


kubetest Up 15m45s

kops validate cluster failed: error during /tmp/kops3324553442/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=30
+ wait 30
+ /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 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=e2d92f00b52f479d5f0a133ec68264b2
sha512sum(kubernetes-test-linux-amd64.tar.gz)=c582cd48f4d52f1fb852bf99611cae1c6b2f465c670bc0ad1e2db6b196317709977f941f68213170c93573d1bede50ff5bd70619bdc278b2430d1e874fbb28fc

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/20 07:18:55 process.go:155: Step './get-kube.sh' finished in 27.172645805s
2021/10/20 07:18:55 process.go:153: Running: /tmp/kops3324553442/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/20 07:18:56 process.go:155: Step '/tmp/kops3324553442/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 536.183733ms
2021/10/20 07:18:56 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/20 07:18:56 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/20 07:18:56 util.go:68: curl https://ip.jsb.workers.dev
2021/10/20 07:18:56 kops.go:439: Using external IP for admin access: 35.193.248.142/32
2021/10/20 07:18:56 process.go:153: Running: /tmp/kops3324553442/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-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.414+c6eedc74a7b4ee --admin-access 35.193.248.142/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
I1020 07:18:56.323862     986 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1020 07:18:56.344030     986 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1020 07:18:56.863298     986 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 32 lines ...

2021/10/20 07:19:29 process.go:155: Step '/tmp/kops3324553442/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-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.414+c6eedc74a7b4ee --admin-access 35.193.248.142/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 32.738123656s
2021/10/20 07:19:29 process.go:153: Running: /tmp/kops3324553442/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1020 07:19:29.062440    1006 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1020 07:19:30.769540    1006 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-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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

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

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
W1020 07:20:00.870209    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:20:10.900513    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:20:20.934034    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:20:30.988893    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:20:41.023405    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:20:51.113787    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:21:01.145788    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:21:11.219516    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:21:21.254347    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:21:31.286703    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:21:41.328307    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:21:51.364030    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:22:01.401482    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:22:11.436352    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:22:21.464556    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:22:31.494561    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:22:41.523183    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:22:51.552973    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:23:01.582557    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:23:11.615520    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:23:21.645992    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:23:31.678305    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:23:41.712217    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:23:51.746856    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:24:01.778077    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:24:11.807846    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

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
W1020 07:24:21.841603    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:24:36.572933    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:24:49.891921    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:25:02.961310    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:25:16.005863    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:25:29.139928    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:25:42.251941    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:25:55.357374    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:26:08.409410    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:26:21.592339    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:26:34.733594    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:26:47.942937    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:27:01.063624    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:27:14.252625    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:27:27.429433    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:27:40.607368    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:27:53.685016    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:28:06.772958    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:28:20.042049    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:28:33.994149    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:28:47.292437    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:29:00.533901    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:29:13.705555    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:29:26.933636    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:29:40.066350    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:29:53.439665    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:30:06.754150    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:30:19.936043    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:30:33.323293    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:30:46.512970    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:30:59.707869    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:31:12.894791    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:31:26.085196    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:31:39.829420    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:31:53.017072    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:32:06.163673    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:32:19.440299    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:32:33.250280    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:32:46.344458    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:32:59.527819    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:33:12.739219    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:33:25.940489    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:33:38.997458    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:33:52.084310    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:34:05.172508    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:34:18.288715    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1b	Master	c5.large	1	1	ap-southeast-1b
nodes-ap-southeast-1b	Node	t3.medium	4	4	ap-southeast-1b

... skipping 7 lines ...
Machine	i-075a254591bbec992				machine "i-075a254591bbec992" has not yet joined cluster
Machine	i-07c50fbd765c0a38c				machine "i-07c50fbd765c0a38c" has not yet joined cluster
Machine	i-07cbd417ca2c8bdbe				machine "i-07cbd417ca2c8bdbe" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-rfqj9		system-cluster-critical pod "coredns-6c8944dbdc-rfqj9" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-mvg5s	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-mvg5s" is pending

Validation Failed
W1020 07:34:31.383683    1006 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/20 07:34:41 process.go:155: Step '/tmp/kops3324553442/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m12.349409093s
2021/10/20 07:34:41 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/20 07:34:41 process.go:153: Running: /tmp/kops3324553442/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1020 07:34:41.420944    1019 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/20 07:34:43 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.950481409s
2021/10/20 07:34:43 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-rfqj9
... skipping 40 lines ...
2021/10/20 07:35:04 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/20 07:35:05 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/20 07:35:05 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/20 07:35:06 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/20 07:35:06 dump.go:129: dumping node not registered in kubernetes: 54.151.143.102
2021/10/20 07:35:06 dump.go:163: Dumping node 54.151.143.102
2021/10/20 07:35:07 dump.go:132: error dumping node 54.151.143.102: could not connect: unable to SSH to "54.151.143.102": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 07:35:07 dump.go:129: dumping node not registered in kubernetes: 52.221.242.74
2021/10/20 07:35:07 dump.go:163: Dumping node 52.221.242.74
2021/10/20 07:35:09 dump.go:132: error dumping node 52.221.242.74: could not connect: unable to SSH to "52.221.242.74": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 07:35:09 dump.go:129: dumping node not registered in kubernetes: 54.169.158.56
2021/10/20 07:35:09 dump.go:163: Dumping node 54.169.158.56
2021/10/20 07:35:11 dump.go:132: error dumping node 54.169.158.56: could not connect: unable to SSH to "54.169.158.56": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 07:35:11 dump.go:129: dumping node not registered in kubernetes: 52.221.180.28
2021/10/20 07:35:11 dump.go:163: Dumping node 52.221.180.28
2021/10/20 07:35:12 dump.go:132: error dumping node 52.221.180.28: could not connect: unable to SSH to "52.221.180.28": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/20 07:35:12 process.go:153: Running: /tmp/kops3324553442/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1020 07:35:12.452708    1168 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-southeast-1b
2021/10/20 07:35:12 process.go:155: Step '/tmp/kops3324553442/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 557.681529ms
2021/10/20 07:35:12 process.go:153: Running: /tmp/kops3324553442/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 154 lines ...
dhcp-options:dopt-01ffbd858dbcd90d5	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/20 07:36:18 process.go:155: Step '/tmp/kops3324553442/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m5.79944233s
2021/10/20 07:36:18 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/20 07:36:18 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops3324553442/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 ...