This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-12 19:12
Elapsed18m18s
Revision
job-versionv1.23.0-alpha.3.290+af2ed2569d56a9
kubetest-version
revisionv1.23.0-alpha.3.290+af2ed2569d56a9

Test Failures


kubetest Up 15m45s

kops validate cluster failed: error during /tmp/kops2781633737/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 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=399325fa361d0ce8dd8f2e8970165eb1
sha512sum(kubernetes-test-linux-amd64.tar.gz)=5ae5a046e74fcd4920231f19b85db8a8fb5428e3f50a29651f05acaf1fb75f4db6c58068cebc57b5491d9cdcf4aba6804e19640e5c904b6550807d611bc77ec9

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/12 19:13:03 process.go:155: Step './get-kube.sh' finished in 27.804662576s
2021/10/12 19:13:03 process.go:153: Running: /tmp/kops2781633737/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/12 19:13:04 process.go:155: Step '/tmp/kops2781633737/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 531.481265ms
2021/10/12 19:13:04 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/12 19:13:04 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/12 19:13:04 util.go:68: curl https://ip.jsb.workers.dev
2021/10/12 19:13:04 kops.go:439: Using external IP for admin access: 34.134.86.254/32
2021/10/12 19:13:04 process.go:153: Running: /tmp/kops2781633737/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.290+af2ed2569d56a9 --admin-access 34.134.86.254/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
I1012 19:13:04.151688     987 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 19:13:04.178144     987 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1012 19:13:04.661952     987 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 32 lines ...

2021/10/12 19:13:36 process.go:155: Step '/tmp/kops2781633737/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-1c --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.290+af2ed2569d56a9 --admin-access 34.134.86.254/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.194241632s
2021/10/12 19:13:36 process.go:153: Running: /tmp/kops2781633737/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1012 19:13:36.347207    1008 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1012 19:13:38.010920    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
W1012 19:13:48.042318    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-1c	Master	c5.large	1	1	ap-southeast-1c
nodes-ap-southeast-1c	Node	t3.medium	4	4	ap-southeast-1c

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

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

... skipping 7 lines ...
Machine	i-0c16b020a21418f3d				machine "i-0c16b020a21418f3d" has not yet joined cluster
Machine	i-0dc2c07d832e28bf9				machine "i-0dc2c07d832e28bf9" has not yet joined cluster
Machine	i-0e52abdbd59223a29				machine "i-0e52abdbd59223a29" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-26vmq		system-cluster-critical pod "coredns-6c8944dbdc-26vmq" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jfn6x	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jfn6x" is pending

Validation Failed
W1012 19:28:39.354990    1008 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/12 19:28:49 process.go:155: Step '/tmp/kops2781633737/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m13.040294802s
2021/10/12 19:28:49 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/12 19:28:49 process.go:153: Running: /tmp/kops2781633737/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1012 19:28:49.388997    1022 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/12 19:28:51 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.955382784s
2021/10/12 19:28:51 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-26vmq
... skipping 40 lines ...
2021/10/12 19:29:12 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/12 19:29:12 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/12 19:29:13 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/12 19:29:13 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/12 19:29:13 dump.go:129: dumping node not registered in kubernetes: 13.212.15.175
2021/10/12 19:29:13 dump.go:163: Dumping node 13.212.15.175
2021/10/12 19:29:15 dump.go:132: error dumping node 13.212.15.175: could not connect: unable to SSH to "13.212.15.175": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 19:29:15 dump.go:129: dumping node not registered in kubernetes: 13.212.183.133
2021/10/12 19:29:15 dump.go:163: Dumping node 13.212.183.133
2021/10/12 19:29:17 dump.go:132: error dumping node 13.212.183.133: could not connect: unable to SSH to "13.212.183.133": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 19:29:17 dump.go:129: dumping node not registered in kubernetes: 13.212.125.131
2021/10/12 19:29:17 dump.go:163: Dumping node 13.212.125.131
2021/10/12 19:29:18 dump.go:132: error dumping node 13.212.125.131: could not connect: unable to SSH to "13.212.125.131": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 19:29:18 dump.go:129: dumping node not registered in kubernetes: 18.140.248.121
2021/10/12 19:29:18 dump.go:163: Dumping node 18.140.248.121
2021/10/12 19:29:20 dump.go:132: error dumping node 18.140.248.121: could not connect: unable to SSH to "18.140.248.121": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/12 19:29:20 process.go:153: Running: /tmp/kops2781633737/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1012 19:29:20.177330    1169 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	ap-southeast-1c
2021/10/12 19:29:20 process.go:155: Step '/tmp/kops2781633737/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 470.475129ms
2021/10/12 19:29:20 process.go:153: Running: /tmp/kops2781633737/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 182 lines ...
dhcp-options:dopt-0e97db185044fb54c	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/12 19:30:47 process.go:155: Step '/tmp/kops2781633737/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m27.139643542s
2021/10/12 19:30:47 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/12 19:30:47 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2781633737/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 ...