This job view page is being replaced by Spyglass soon. Check out the new job view.
PRReillyBrogan: Add bidirectional BPF mount for Cilium >= 1.9.10 or >= 1.10.4
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-25 00:24
Elapsed24m12s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 525 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0925 00:27:45.835073    4809 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/d19caa87-1d96-11ec-86ce-767084cdd143/kops
I0925 00:27:45.960969    4809 up.go:43] Cleaning up any leaked resources from previous cluster
I0925 00:27:45.961023    4809 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0925 00:27:45.975680   12398 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 00:27:45.975760   12398 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0925 00:27:46.417695    4809 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0925 00:27:46.417748    4809 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --yes
I0925 00:27:46.431141   12408 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 00:27:46.431219   12408 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
I0925 00:27:46.896464    4809 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/25 00:27:46 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
I0925 00:27:46.903868    4809 http.go:37] curl https://ip.jsb.workers.dev
I0925 00:27:46.987426    4809 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.2 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210907 --channel=alpha --networking=weave --container-runtime=containerd --node-size=t3.large --admin-access 23.251.157.57/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I0925 00:27:47.002410   12418 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 00:27:47.002472   12418 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0925 00:27:47.020123   12418 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0925 00:27:47.555405   12418 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 32 lines ...

I0925 00:28:19.182877    4809 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0925 00:28:19.196840   12437 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 00:28:19.197013   12437 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0925 00:28:20.799212   12437 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0925 00:28:30.840279   12437 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.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.large	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
W0925 00:28:40.872237   12437 validate_cluster.go:232] (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.large	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
W0925 00:28:50.915361   12437 validate_cluster.go:232] (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.large	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
W0925 00:29:00.941540   12437 validate_cluster.go:232] (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.large	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
W0925 00:29:10.986290   12437 validate_cluster.go:232] (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.large	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
W0925 00:29:21.029594   12437 validate_cluster.go:232] (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.large	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
W0925 00:29:31.058302   12437 validate_cluster.go:232] (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.large	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
W0925 00:29:41.087008   12437 validate_cluster.go:232] (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.large	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
W0925 00:29:51.147855   12437 validate_cluster.go:232] (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.large	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
W0925 00:30:01.189154   12437 validate_cluster.go:232] (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.large	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
W0925 00:30:11.219204   12437 validate_cluster.go:232] (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.large	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
W0925 00:30:21.249204   12437 validate_cluster.go:232] (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.large	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
W0925 00:30:31.284582   12437 validate_cluster.go:232] (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.large	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
W0925 00:30:41.312501   12437 validate_cluster.go:232] (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.large	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
W0925 00:30:51.342169   12437 validate_cluster.go:232] (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.large	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
W0925 00:31:01.404787   12437 validate_cluster.go:232] (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.large	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
W0925 00:31:11.433355   12437 validate_cluster.go:232] (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.large	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
W0925 00:31:21.463275   12437 validate_cluster.go:232] (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.large	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
W0925 00:31:31.492128   12437 validate_cluster.go:232] (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.large	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
W0925 00:31:41.535994   12437 validate_cluster.go:232] (will retry): cluster not yet healthy
W0925 00:31:51.565032   12437 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.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.large	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
W0925 00:32:01.594177   12437 validate_cluster.go:232] (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.large	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
W0925 00:32:11.622988   12437 validate_cluster.go:232] (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.large	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
W0925 00:32:21.659194   12437 validate_cluster.go:232] (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.large	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
W0925 00:32:31.690961   12437 validate_cluster.go:232] (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.large	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
W0925 00:32:41.723031   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 11 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lpbf5	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lpbf5" is pending
Pod	kube-system/ebs-csi-node-msgx9			system-node-critical pod "ebs-csi-node-msgx9" is pending
Pod	kube-system/ebs-csi-node-zk8nl			system-node-critical pod "ebs-csi-node-zk8nl" is pending
Pod	kube-system/weave-net-466cp			system-node-critical pod "weave-net-466cp" is pending
Pod	kube-system/weave-net-ckjd6			system-node-critical pod "weave-net-ckjd6" is pending

Validation Failed
W0925 00:32:56.188097   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 18 lines ...
Pod	kube-system/ebs-csi-node-zk8nl				system-node-critical pod "ebs-csi-node-zk8nl" is pending
Pod	kube-system/weave-net-466cp				system-node-critical pod "weave-net-466cp" is pending
Pod	kube-system/weave-net-69xjq				system-node-critical pod "weave-net-69xjq" is pending
Pod	kube-system/weave-net-ckjd6				system-node-critical pod "weave-net-ckjd6" is pending
Pod	kube-system/weave-net-wjv9c				system-node-critical pod "weave-net-wjv9c" is pending

Validation Failed
W0925 00:33:09.249438   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 14 lines ...
Pod	kube-system/ebs-csi-node-cmmc9				system-node-critical pod "ebs-csi-node-cmmc9" is pending
Pod	kube-system/ebs-csi-node-fft7x				system-node-critical pod "ebs-csi-node-fft7x" is pending
Pod	kube-system/ebs-csi-node-msgx9				system-node-critical pod "ebs-csi-node-msgx9" is pending
Pod	kube-system/ebs-csi-node-zk8nl				system-node-critical pod "ebs-csi-node-zk8nl" is pending
Pod	kube-system/weave-net-69xjq				system-node-critical pod "weave-net-69xjq" is pending

Validation Failed
W0925 00:33:22.481904   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is pending

Validation Failed
W0925 00:33:35.638047   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4					system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-45-20.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-45-20.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-57-177.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-57-177.ap-southeast-1.compute.internal" is pending

Validation Failed
W0925 00:33:48.846149   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4					system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-63-46.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-63-46.ap-southeast-1.compute.internal" is pending

Validation Failed
W0925 00:34:01.969782   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:34:15.092796   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:34:28.238104   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:34:41.510487   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:34:54.683980   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:35:07.825822   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:35:20.900650   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)

Validation Failed
W0925 00:35:34.066948   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:35:47.132352   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:36:00.167905   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:36:13.322532   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:36:26.441525   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)

Validation Failed
W0925 00:36:39.613539   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:36:53.405098   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:37:06.455799   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:37:19.682669   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:37:32.875931   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:37:45.994934   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:37:59.115383   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)

Validation Failed
W0925 00:38:12.237838   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:38:25.370739   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:38:38.498507   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:38:51.713329   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:39:04.958235   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:39:18.162798   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:39:31.537807   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:39:44.811762   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:39:58.017499   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:40:11.079014   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:40:24.367856   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:40:37.658060   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:40:51.456368   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:41:04.622923   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:41:17.712393   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)

Validation Failed
W0925 00:41:30.922976   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 6 lines ...
ip-172-20-63-46.ap-southeast-1.compute.internal		node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)

Validation Failed
W0925 00:41:44.112905   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)

Validation Failed
W0925 00:41:57.195571   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:42:10.327907   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:42:23.568447   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:42:36.774938   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:42:49.904682   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:43:03.066891   12437 validate_cluster.go:232] (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.large	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-j6vl4	system-cluster-critical pod "coredns-5dc785954d-j6vl4" is not ready (coredns)
Pod	kube-system/ebs-csi-node-cmmc9		system-node-critical pod "ebs-csi-node-cmmc9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-fft7x		system-node-critical pod "ebs-csi-node-fft7x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-msgx9		system-node-critical pod "ebs-csi-node-msgx9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zk8nl		system-node-critical pod "ebs-csi-node-zk8nl" is not ready (ebs-plugin)

Validation Failed
W0925 00:43:16.189337   12437 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0925 00:43:26.194887    4809 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0925 00:43:26.208636   12449 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 00:43:26.208704   12449 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/25 00:43:40 Dumping node ip-172-20-36-185.ap-southeast-1.compute.internal
2021/09/25 00:43:52 Dumping node ip-172-20-45-20.ap-southeast-1.compute.internal
2021/09/25 00:44:01 Dumping node ip-172-20-49-253.ap-southeast-1.compute.internal
... skipping 1443 lines ...
route-table:rtb-06fb48b8fad5981ef	ok
vpc:vpc-0b13b4e52e89d9f2f	ok
dhcp-options:dopt-00030ff5e34523579	ok
Deleted kubectl config for e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

Deleted cluster: "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...