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-24 21:42
Elapsed24m38s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 535 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0924 21:46:58.348541    4840 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/3ce28efa-1d80-11ec-84bb-6ed1fb6bf5dc/kops
I0924 21:46:58.516616    4840 up.go:43] Cleaning up any leaked resources from previous cluster
I0924 21:46:58.516670    4840 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
I0924 21:46:58.533918   12409 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 21:46:58.534006   12409 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0924 21:46:59.025336    4840 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0924 21:46:59.025412    4840 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
I0924 21:46:59.042001   12419 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 21:46:59.042122   12419 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
I0924 21:46:59.511749    4840 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/24 21:46:59 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
I0924 21:46:59.519435    4840 http.go:37] curl https://ip.jsb.workers.dev
I0924 21:46:59.608563    4840 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 35.239.42.193/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I0924 21:46:59.625050   12430 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 21:46:59.625225   12430 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0924 21:46:59.649242   12430 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0924 21:47:00.227146   12430 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 30 lines ...

I0924 21:47:19.811039    4840 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
I0924 21:47:19.829162   12451 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 21:47:19.829286   12451 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0924 21:47:21.472378   12451 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
W0924 21:47:31.516392   12451 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
W0924 21:47:41.547499   12451 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
W0924 21:47:51.579416   12451 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
W0924 21:48:01.611030   12451 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
W0924 21:48:11.683634   12451 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
W0924 21:48:21.750007   12451 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
W0924 21:48:31.795049   12451 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
W0924 21:48:41.829387   12451 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
W0924 21:48:51.886178   12451 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
W0924 21:49:01.933460   12451 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
W0924 21:49:11.969332   12451 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
W0924 21:49:22.030497   12451 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
W0924 21:49:32.063867   12451 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
W0924 21:49:42.098275   12451 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
W0924 21:49:52.140840   12451 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
W0924 21:50:02.187306   12451 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
W0924 21:50:12.221329   12451 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
W0924 21:50:22.252647   12451 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
W0924 21:50:32.283676   12451 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
W0924 21:50:42.312151   12451 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
W0924 21:50:52.357543   12451 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
W0924 21:51:02.386852   12451 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
W0924 21:51:12.448228   12451 validate_cluster.go:232] (will retry): cluster not yet healthy
W0924 21:51:52.484664   12451 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
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
... skipping 8 lines ...
KIND	NAME							MESSAGE
Node	ip-172-20-50-157.ap-southeast-1.compute.internal	node "ip-172-20-50-157.ap-southeast-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-5dc785954d-cc4zt			system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-dpssp				system-node-critical pod "ebs-csi-node-dpssp" is pending
Pod	kube-system/ebs-csi-node-ngx7c				system-node-critical pod "ebs-csi-node-ngx7c" is pending

Validation Failed
W0924 21:52:07.122154   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:52:20.330937   12451 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-cc4zt					system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-41-173.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-41-173.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-59-226.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-59-226.ap-southeast-1.compute.internal" is pending

Validation Failed
W0924 21:52:33.602149   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:52:46.772044   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:52:59.926376   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:53:13.179997   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:53:26.327390   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:53:39.524306   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:53:52.677337   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:54:06.234775   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)

Validation Failed
W0924 21:54:19.398121   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:54:32.665936   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:54:45.939815   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:54:59.126329   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:55:12.342789   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:55:25.560801   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:55:38.754577   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:55:51.922561   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:56:05.726486   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:56:18.936086   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:56:32.123228   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:56:45.316903   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 21:56:58.538819   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)

Validation Failed
W0924 21:57:11.854152   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:57:25.211562   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:57:38.428268   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:57:51.533005   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:58:04.717332   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:58:18.116817   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:58:31.365986   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:58:44.561106   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:58:57.774673   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:59:11.015637   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:59:24.338102   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:59:37.497672   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 21:59:50.666215   12451 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-59-226.ap-southeast-1.compute.internal	node	True

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

Validation Failed
W0924 22:00:04.753040   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)

Validation Failed
W0924 22:00:17.912531   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)

Validation Failed
W0924 22:00:31.013380   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:00:44.222100   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:00:57.392651   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:01:10.723979   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:01:23.843615   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:01:37.069518   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:01:50.193251   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:02:03.409248   12451 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-cc4zt	system-cluster-critical pod "coredns-5dc785954d-cc4zt" is not ready (coredns)
Pod	kube-system/ebs-csi-node-49w8d		system-node-critical pod "ebs-csi-node-49w8d" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-dpssp		system-node-critical pod "ebs-csi-node-dpssp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-f25vh		system-node-critical pod "ebs-csi-node-f25vh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ngx7c		system-node-critical pod "ebs-csi-node-ngx7c" is not ready (ebs-plugin)

Validation Failed
W0924 22:02:16.627867   12451 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0924 22:02:26.635208    4840 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
I0924 22:02:26.651701   12461 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 22:02:26.651817   12461 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/24 22:02:40 Dumping node ip-172-20-35-151.ap-southeast-1.compute.internal
2021/09/24 22:02:49 Dumping node ip-172-20-41-173.ap-southeast-1.compute.internal
2021/09/24 22:02:58 Dumping node ip-172-20-50-157.ap-southeast-1.compute.internal
... skipping 1423 lines ...
route-table:rtb-0ef91eb4f3baf4446	ok
vpc:vpc-0e6f67ba63f7a450b	ok
dhcp-options:dopt-015d13d63afe88092	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 ...