This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-10-16 18:32
Elapsed18m24s
Revision
job-versionv1.20.0-alpha.1
revisionv1.20.0-alpha.1

Test Failures


Up 15m32s

kops validate cluster failed: error during /tmp/kops931374612/kops validate cluster e2e-kops-flanl-centos7.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
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --deployment=kops --kops-ssh-user=centos --env=KUBE_SSH_USER=centos --env=KOPS_DEPLOY_LATEST_URL=https://storage.googleapis.com/kubernetes-release/release/latest.txt --env=KOPS_KUBE_RELEASE_URL=https://storage.googleapis.com/kubernetes-release/release --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=release/latest --ginkgo-parallel --kops-args=--networking=flannel '--kops-image=679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4' --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort|Services.*rejected.*endpoints|Services.*affinity' --timeout=60m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
AWS_DEFAULT_PROFILE=default
AWS_PROFILE=default
... skipping 146 lines ...
2020/10/16 18:33:17 process.go:155: Step './get-kube.sh' finished in 14.251618855s
2020/10/16 18:33:17 process.go:153: Running: /tmp/kops931374612/kops get clusters e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

cluster not found "e2e-kops-flanl-centos7.test-cncf-aws.k8s.io"
2020/10/16 18:33:18 process.go:155: Step '/tmp/kops931374612/kops get clusters e2e-kops-flanl-centos7.test-cncf-aws.k8s.io' finished in 524.514167ms
2020/10/16 18:33:18 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2020/10/16 18:33:18 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
2020/10/16 18:33:18 util.go:68: curl https://ip.jsb.workers.dev
2020/10/16 18:33:18 kops.go:439: Using external IP for admin access: 35.223.21.240/32
2020/10/16 18:33:18 process.go:153: Running: /tmp/kops931374612/kops create cluster --name e2e-kops-flanl-centos7.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-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.0-alpha.1 --admin-access 35.223.21.240/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1016 18:33:18.568533     154 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I1016 18:33:18.630170     154 create_cluster.go:711] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1016 18:33:19.993267     154 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet ap-southeast-1a
... skipping 38 lines ...

2020/10/16 18:33:37 process.go:155: Step '/tmp/kops931374612/kops create cluster --name e2e-kops-flanl-centos7.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-1a --master-size c5.large --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.0-alpha.1 --admin-access 35.223.21.240/32 --image 679593333241/CentOS Linux 7 x86_64 HVM EBS ENA 2002_01-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-0042af67f8e4dcc20.4 --cloud aws --networking=flannel --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 19.392158249s
2020/10/16 18:33:37 process.go:153: Running: /tmp/kops931374612/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m
I1016 18:33:37.957836     176 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

W1016 18:33:39.563886     176 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-flanl-centos7.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

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

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1016 18:38:10.797967     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:38:24.205981     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
Machine	i-0b850188efe6ee719					machine "i-0b850188efe6ee719" has not yet joined cluster
Machine	i-0c39653d08c470470					machine "i-0c39653d08c470470" has not yet joined cluster
Machine	i-0f15d1f93d6fd530b					machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending

Validation Failed
W1016 18:38:24.796378     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:38:36.886330     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
Machine	i-0b850188efe6ee719					machine "i-0b850188efe6ee719" has not yet joined cluster
Machine	i-0c39653d08c470470					machine "i-0c39653d08c470470" has not yet joined cluster
Machine	i-0f15d1f93d6fd530b					machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending

Validation Failed
W1016 18:38:37.274365     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:38:49.364502     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
Machine	i-0b850188efe6ee719					machine "i-0b850188efe6ee719" has not yet joined cluster
Machine	i-0c39653d08c470470					machine "i-0c39653d08c470470" has not yet joined cluster
Machine	i-0f15d1f93d6fd530b					machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending

Validation Failed
W1016 18:38:49.562203     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:39:01.589450     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
Machine	i-0b850188efe6ee719					machine "i-0b850188efe6ee719" has not yet joined cluster
Machine	i-0c39653d08c470470					machine "i-0c39653d08c470470" has not yet joined cluster
Machine	i-0f15d1f93d6fd530b					machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending

Validation Failed
W1016 18:39:01.786823     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:39:13.864543     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
Machine	i-0b850188efe6ee719					machine "i-0b850188efe6ee719" has not yet joined cluster
Machine	i-0c39653d08c470470					machine "i-0c39653d08c470470" has not yet joined cluster
Machine	i-0f15d1f93d6fd530b					machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending

Validation Failed
W1016 18:39:14.063837     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:39:26.094167     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
Machine	i-0b850188efe6ee719					machine "i-0b850188efe6ee719" has not yet joined cluster
Machine	i-0c39653d08c470470					machine "i-0c39653d08c470470" has not yet joined cluster
Machine	i-0f15d1f93d6fd530b					machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending

Validation Failed
W1016 18:39:26.293180     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:39:38.367333     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 16 lines ...
Pod	kube-system/kube-flannel-ds-v68cr					system-node-critical pod "kube-flannel-ds-v68cr" is pending
Pod	kube-system/kube-flannel-ds-zmztz					system-node-critical pod "kube-flannel-ds-zmztz" is pending
Pod	kube-system/kube-proxy-ip-172-20-44-123.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-44-123.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-44-194.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-44-194.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-48.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-48.ap-southeast-1.compute.internal" is pending

Validation Failed
W1016 18:39:38.566243     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:39:50.610038     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 12 lines ...
Node	ip-172-20-44-194.ap-southeast-1.compute.internal	node "ip-172-20-44-194.ap-southeast-1.compute.internal" is not ready
Node	ip-172-20-61-48.ap-southeast-1.compute.internal		node "ip-172-20-61-48.ap-southeast-1.compute.internal" is not ready
Pod	kube-system/kube-dns-696cb84c7-vwqb2			system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-4x946	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-4x946" is pending
Pod	kube-system/kube-flannel-ds-v68cr			system-node-critical pod "kube-flannel-ds-v68cr" is pending

Validation Failed
W1016 18:39:50.809132     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:40:02.932934     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Machine	i-0f15d1f93d6fd530b			machine "i-0f15d1f93d6fd530b" has not yet joined cluster
Pod	kube-system/kube-dns-696cb84c7-7zkd6	system-cluster-critical pod "kube-dns-696cb84c7-7zkd6" is pending
Pod	kube-system/kube-dns-696cb84c7-vwqb2	system-cluster-critical pod "kube-dns-696cb84c7-vwqb2" is not ready (kubedns)

Validation Failed
W1016 18:40:03.141312     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:40:15.258189     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:40:15.459397     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:40:28.557978     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:40:28.760455     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:40:40.775601     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:40:40.976163     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:40:53.028306     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:40:53.229110     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:41:05.323228     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:41:05.526592     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:41:17.526018     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:41:17.728508     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:41:29.800988     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:41:30.001367     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:41:42.077755     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:41:42.279240     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:41:54.333707     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:41:54.534818     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:42:06.628128     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:42:06.828521     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:42:19.543580     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:42:19.763072     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:42:31.836039     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:42:32.042893     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:42:44.134809     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:42:44.348966     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:42:56.417706     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:42:56.621529     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:43:08.666417     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:43:08.868535     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:43:20.915279     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:43:21.116923     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:43:33.140691     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:43:33.342983     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:43:45.474915     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:43:45.676376     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:43:57.712142     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:43:57.912663     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:44:09.920017     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:44:10.122574     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:44:22.126860     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:44:22.339933     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:44:34.416132     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:44:34.619157     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:44:46.662982     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:44:46.867336     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:44:58.922651     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:44:59.123184     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:45:11.138140     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:45:11.341155     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:45:23.373934     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:45:23.574983     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:45:35.678113     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:45:35.878580     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:45:47.903773     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:45:48.105939     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:46:00.141474     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:46:00.344156     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:46:13.010231     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:46:13.217284     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:46:25.386003     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:46:25.593076     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:46:37.642762     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:46:37.843252     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:46:49.861002     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:46:50.062352     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:47:02.125772     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:47:02.326470     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:47:14.384228     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:47:14.586653     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:47:26.725885     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:47:26.926771     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:47:38.970060     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:47:39.170894     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:47:51.275901     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:47:51.476646     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:48:03.643409     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:48:03.846428     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:48:15.951148     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:48:16.151896     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:48:28.255191     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:48:28.456364     176 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 18:48:40.475899     176 warnings.go:67] v1 ComponentStatus is deprecated in v1.19+
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a
... skipping 6 lines ...
ip-172-20-61-48.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME			MESSAGE
Machine	i-0f15d1f93d6fd530b	machine "i-0f15d1f93d6fd530b" has not yet joined cluster

Validation Failed
W1016 18:48:40.678166     176 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
2020/10/16 18:48:50 process.go:155: Step '/tmp/kops931374612/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m' finished in 15m12.747639734s
2020/10/16 18:48:50 process.go:153: Running: kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller
2020/10/16 18:48:50 process.go:153: Running: /tmp/kops931374612/kops toolbox dump --name e2e-kops-flanl-centos7.test-cncf-aws.k8s.io -ojson
I1016 18:48:50.715645     189 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
2020/10/16 18:48:52 process.go:155: Step 'kubectl -n kube-system get pods -ojson -l k8s-app=kops-controller' finished in 1.826158639s
2020/10/16 18:48:52 process.go:153: Running: kubectl -n kube-system logs --all-containers kops-controller-8spcf
... skipping 209 lines ...
	route-table:rtb-0a1b9f0489b8ab7ee
	volume:vol-0d416b0019836cc6b
	security-group:sg-0af65bf1e912a5637
	security-group:sg-02f677d3a18ae521b
	vpc:vpc-0819377e33c041bad
	volume:vol-0bc063d1b4940e8b2
I1016 18:50:40.871198     241 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0d416b0019836cc6b	ok
volume:vol-0bc063d1b4940e8b2	still has dependencies, will retry
volume:vol-0aed6e782a43ec029	ok
volume:vol-0ce64c5ed908343d2	still has dependencies, will retry
volume:vol-01f24097c4d14ae42	ok
volume:vol-03bb068dfc1a4d8a8	ok
... skipping 24 lines ...
	subnet:subnet-0768909420905527a
	dhcp-options:dopt-0edc8b0273da15c19
	internet-gateway:igw-0398f4da92624f40b
	route-table:rtb-0a1b9f0489b8ab7ee
	security-group:sg-0af65bf1e912a5637
subnet:subnet-0768909420905527a	still has dependencies, will retry
I1016 18:51:03.426857     241 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0ce64c5ed908343d2	ok
volume:vol-0bc063d1b4940e8b2	still has dependencies, will retry
internet-gateway:igw-0398f4da92624f40b	still has dependencies, will retry
security-group:sg-0af65bf1e912a5637	still has dependencies, will retry
Not all resources deleted; waiting before reattempting deletion
	subnet:subnet-0768909420905527a
	dhcp-options:dopt-0edc8b0273da15c19
	internet-gateway:igw-0398f4da92624f40b
	route-table:rtb-0a1b9f0489b8ab7ee
	security-group:sg-0af65bf1e912a5637
	vpc:vpc-0819377e33c041bad
	volume:vol-0bc063d1b4940e8b2
I1016 18:51:14.674730     241 errors.go:32] unexpected aws error code: "InvalidVolume.NotFound"
volume:vol-0bc063d1b4940e8b2	ok
subnet:subnet-0768909420905527a	ok
security-group:sg-0af65bf1e912a5637	ok
internet-gateway:igw-0398f4da92624f40b	ok
route-table:rtb-0a1b9f0489b8ab7ee	ok
vpc:vpc-0819377e33c041bad	ok
dhcp-options:dopt-0edc8b0273da15c19	ok
Deleted kubectl config for e2e-kops-flanl-centos7.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-flanl-centos7.test-cncf-aws.k8s.io"
2020/10/16 18:51:21 process.go:155: Step '/tmp/kops931374612/kops delete cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --yes' finished in 1m39.775102715s
2020/10/16 18:51:21 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/10/16 18:51:21 main.go:312: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops931374612/kops validate cluster e2e-kops-flanl-centos7.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 720, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 570, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...