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 03:04
Elapsed23m46s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 515 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0925 03:07:15.635689    4872 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/2b7e9cfe-1dad-11ec-86ce-767084cdd143/kops
I0925 03:07:15.755189    4872 up.go:43] Cleaning up any leaked resources from previous cluster
I0925 03:07:15.755226    4872 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 03:07:15.769765   12441 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 03:07:15.770229   12441 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0925 03:07:16.197169    4872 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0925 03:07:16.197224    4872 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 03:07:16.210319   12451 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 03:07:16.210927   12451 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 03:07:16.647234    4872 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/25 03:07:16 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 03:07:16.655090    4872 http.go:37] curl https://ip.jsb.workers.dev
I0925 03:07:16.740536    4872 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 34.135.157.253/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0925 03:07:16.752126   12461 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 03:07:16.752302   12461 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0925 03:07:16.772821   12461 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0925 03:07:17.335023   12461 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 32 lines ...

I0925 03:07:48.027564    4872 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 03:07:48.040797   12480 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 03:07:48.040880   12480 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0925 03:07:49.598251   12480 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-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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 03:07:59.644369   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

... skipping 9 lines ...
Machine	i-0fe548142f69a69be				machine "i-0fe548142f69a69be" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-q4zf7		system-cluster-critical pod "coredns-5dc785954d-q4zf7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-h8z99	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-h8z99" is pending
Pod	kube-system/ebs-csi-node-mftkb			system-node-critical pod "ebs-csi-node-mftkb" is pending
Pod	kube-system/weave-net-pg5hj			system-node-critical pod "weave-net-pg5hj" is pending

Validation Failed
W0925 03:12:15.189955   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-mftkb				system-node-critical pod "ebs-csi-node-mftkb" is pending
Pod	kube-system/ebs-csi-node-qx48q				system-node-critical pod "ebs-csi-node-qx48q" is pending
Pod	kube-system/weave-net-g9pvn				system-node-critical pod "weave-net-g9pvn" is pending
Pod	kube-system/weave-net-lltcl				system-node-critical pod "weave-net-lltcl" is pending
Pod	kube-system/weave-net-pg5hj				system-node-critical pod "weave-net-pg5hj" is pending

Validation Failed
W0925 03:12:28.278629   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 13 lines ...
Pod	kube-system/ebs-csi-node-87mqp			system-node-critical pod "ebs-csi-node-87mqp" is pending
Pod	kube-system/ebs-csi-node-8mb7r			system-node-critical pod "ebs-csi-node-8mb7r" is pending
Pod	kube-system/ebs-csi-node-mftkb			system-node-critical pod "ebs-csi-node-mftkb" is pending
Pod	kube-system/ebs-csi-node-qx48q			system-node-critical pod "ebs-csi-node-qx48q" is pending
Pod	kube-system/weave-net-5brjc			system-node-critical pod "weave-net-5brjc" is pending

Validation Failed
W0925 03:12:41.343179   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 7 lines ...

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

Validation Failed
W0925 03:12:54.432628   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 7 lines ...

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

Validation Failed
W0925 03:13:07.470960   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:13:20.500808   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 7 lines ...

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

Validation Failed
W0925 03:13:33.536407   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:13:46.551492   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:13:59.670113   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:14:12.644205   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

Validation Failed
W0925 03:14:25.652630   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:14:38.737452   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:14:51.723583   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 7 lines ...

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

Validation Failed
W0925 03:15:04.763762   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:15:17.789685   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:15:30.792823   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 6 lines ...
ip-172-20-61-197.ap-southeast-2.compute.internal	node	True

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

Validation Failed
W0925 03:15:43.958868   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

Validation Failed
W0925 03:15:57.008052   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:16:10.646101   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:16:23.665450   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:16:36.701283   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:16:49.677904   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:17:02.661282   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:17:15.988771   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 7 lines ...

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

Validation Failed
W0925 03:17:29.106851   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

Validation Failed
W0925 03:17:42.124657   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

Validation Failed
W0925 03:17:55.136799   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:18:08.179634   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:18:21.136848   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:18:34.077526   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:18:47.116469   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:19:00.062104   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:19:13.251895   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:19:26.320847   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:19:39.299750   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:19:52.219815   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:20:05.899308   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:20:19.019617   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

Validation Failed
W0925 03:20:32.007404   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 7 lines ...

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

Validation Failed
W0925 03:20:45.138325   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

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

Validation Failed
W0925 03:20:58.164756   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:21:11.433586   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:21:24.445572   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:21:37.456835   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:21:50.498294   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:22:03.640341   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:22:16.666354   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:22:29.683224   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.large	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-q4zf7	system-cluster-critical pod "coredns-5dc785954d-q4zf7" is not ready (coredns)
Pod	kube-system/ebs-csi-node-87mqp		system-node-critical pod "ebs-csi-node-87mqp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8mb7r		system-node-critical pod "ebs-csi-node-8mb7r" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mftkb		system-node-critical pod "ebs-csi-node-mftkb" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-qx48q		system-node-critical pod "ebs-csi-node-qx48q" is not ready (ebs-plugin)

Validation Failed
W0925 03:22:42.751475   12480 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0925 03:22:52.759382    4872 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 03:22:52.771125   12490 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0925 03:22:52.771317   12490 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/25 03:23:05 Dumping node ip-172-20-33-37.ap-southeast-2.compute.internal
2021/09/25 03:23:14 Dumping node ip-172-20-42-55.ap-southeast-2.compute.internal
2021/09/25 03:23:23 Dumping node ip-172-20-53-59.ap-southeast-2.compute.internal
... skipping 1437 lines ...
route-table:rtb-0064b270074bb949a	ok
vpc:vpc-075ee14081ae67077	ok
dhcp-options:dopt-09b68be1405888905	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 ...