This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-09-21 04:22
Elapsed20m23s
Revisionmaster

Test Failures


kubetest2 Up 15m55s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 166 lines ...
I0921 04:23:46.548727    6075 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.24/latest-ci-updown-green.txt
I0921 04:23:46.550731    6075 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.24.4+v1.24.2-16-gdadb6495cd/linux/amd64/kops
I0921 04:23:47.138578    6075 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519
I0921 04:23:47.154155    6075 up.go:44] Cleaning up any leaked resources from previous cluster
I0921 04:23:47.154265    6075 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0921 04:23:47.154300    6075 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0921 04:23:47.607265    6075 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0921 04:23:47.607315    6075 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --yes
I0921 04:23:47.607329    6075 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --yes
I0921 04:23:47.627923    6109 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io" not found
I0921 04:23:48.098648    6075 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/21 04:23:48 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
I0921 04:23:48.115016    6075 http.go:37] curl https://ip.jsb.workers.dev
I0921 04:23:48.185556    6075 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.14 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220912 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 104.197.84.180/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0921 04:23:48.185596    6075 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.14 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220912 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 104.197.84.180/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0921 04:23:48.206692    6119 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0921 04:23:48.233061    6119 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0921 04:23:48.733550    6119 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 570 lines ...

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
W0921 04:24:39.796426    6159 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.medium	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
W0921 04:24:49.841628    6159 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.medium	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
W0921 04:24:59.897032    6159 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.medium	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
W0921 04:25:09.938785    6159 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.medium	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
W0921 04:25:19.987315    6159 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.medium	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
W0921 04:25:30.033212    6159 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.medium	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
W0921 04:25:40.089702    6159 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.medium	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
W0921 04:25:50.129935    6159 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.medium	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
W0921 04:26:00.170031    6159 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.medium	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
W0921 04:26:10.229942    6159 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.medium	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
W0921 04:26:20.286951    6159 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.medium	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
W0921 04:26:30.333340    6159 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.medium	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
W0921 04:26:40.377402    6159 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.medium	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
W0921 04:26:50.439672    6159 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.medium	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
W0921 04:27:00.494077    6159 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.medium	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
W0921 04:27:10.539941    6159 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.medium	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
W0921 04:27:20.584430    6159 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.medium	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
W0921 04:27:30.657358    6159 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.medium	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
W0921 04:27:40.709494    6159 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.medium	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
W0921 04:27:50.758771    6159 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.medium	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
W0921 04:28:00.802176    6159 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.medium	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
W0921 04:28:10.839880    6159 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.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/cilium-47dvt			system-node-critical pod "cilium-47dvt" is not ready (cilium-agent)
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-fqthl	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-fqthl" is pending
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is pending
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is pending

Validation Failed
W0921 04:28:25.272086    6159 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.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/cilium-47dvt			system-node-critical pod "cilium-47dvt" is not ready (cilium-agent)
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is pending
Pod	kube-system/coredns-autoscaler-6fccfff6b-fqthl	system-cluster-critical pod "coredns-autoscaler-6fccfff6b-fqthl" is pending
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is pending
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is pending

Validation Failed
W0921 04:28:38.442781    6159 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.medium	4	4	ap-southeast-2a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-2tgkr				system-node-critical pod "ebs-csi-node-2tgkr" is pending
Pod	kube-system/ebs-csi-node-hjr87				system-node-critical pod "ebs-csi-node-hjr87" is pending
Pod	kube-system/ebs-csi-node-k2lsx				system-node-critical pod "ebs-csi-node-k2lsx" is pending
Pod	kube-system/ebs-csi-node-vkd4t				system-node-critical pod "ebs-csi-node-vkd4t" is pending
Pod	kube-system/ebs-csi-node-xbtr8				system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:28:51.361826    6159 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.medium	4	4	ap-southeast-2a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-node-2tgkr				system-node-critical pod "ebs-csi-node-2tgkr" is pending
Pod	kube-system/ebs-csi-node-hjr87				system-node-critical pod "ebs-csi-node-hjr87" is pending
Pod	kube-system/ebs-csi-node-k2lsx				system-node-critical pod "ebs-csi-node-k2lsx" is pending
Pod	kube-system/ebs-csi-node-vkd4t				system-node-critical pod "ebs-csi-node-vkd4t" is pending
Pod	kube-system/ebs-csi-node-xbtr8				system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:29:04.465368    6159 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.medium	4	4	ap-southeast-2a

... skipping 17 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is pending
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is pending
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is pending
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is pending
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:29:17.472199    6159 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.medium	4	4	ap-southeast-2a

... skipping 13 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is pending
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is pending
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is pending
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is pending
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:29:30.486419    6159 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.medium	4	4	ap-southeast-2a

... skipping 13 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is pending
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is pending
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is pending
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is pending
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:29:43.420632    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:29:56.407014    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is pending

Validation Failed
W0921 04:30:09.581580    6159 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.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)

Validation Failed
W0921 04:30:22.544999    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)

Validation Failed
W0921 04:30:35.561234    6159 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.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)

Validation Failed
W0921 04:30:48.666829    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)

Validation Failed
W0921 04:31:01.618519    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:31:14.608485    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:31:27.726843    6159 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.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:31:40.708412    6159 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.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)

Validation Failed
W0921 04:31:53.613814    6159 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.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)

Validation Failed
W0921 04:32:06.714138    6159 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.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:32:20.520279    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:32:33.650752    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:32:46.612518    6159 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.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:32:59.612615    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:33:12.534206    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:33:25.559610    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:33:38.486057    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:33:51.570873    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:34:04.793474    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:34:17.759518    6159 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.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:34:30.680307    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:34:43.873587    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:34:56.892853    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:35:09.855620    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:35:22.801623    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:35:35.765088    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:35:48.847260    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:36:01.966225    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:36:15.658865    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:36:28.715404    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:36:41.832586    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:36:54.930967    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:37:08.020262    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:37:21.224204    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:37:34.328079    6159 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.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:37:47.360595    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:38:00.399326    6159 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.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:38:13.392897    6159 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.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-tmqfp		system-cluster-critical pod "coredns-5b7f7db4db-tmqfp" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:38:26.395112    6159 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.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-ts4s9	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-ts4s9" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)

Validation Failed
W0921 04:38:39.486379    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:38:52.562052    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:39:05.722662    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:39:19.012063    6159 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.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-2tgkr			system-node-critical pod "ebs-csi-node-2tgkr" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hjr87			system-node-critical pod "ebs-csi-node-hjr87" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k2lsx			system-node-critical pod "ebs-csi-node-k2lsx" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-vkd4t			system-node-critical pod "ebs-csi-node-vkd4t" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xbtr8			system-node-critical pod "ebs-csi-node-xbtr8" is not ready (ebs-plugin)

Validation Failed
W0921 04:39:32.056054    6159 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0921 04:39:42.065481    6075 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0921 04:39:42.065567    6075 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0921 04:40:47.216383    6075 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
I0921 04:40:47.216454    6075 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
I0921 04:40:47.803584    6075 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
I0921 04:40:47.803616    6075 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/f14ad21a-3964-11ed-b62f-a2c655ae1569/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
... skipping 295 lines ...
route-table:rtb-06e025921307a0645	ok
vpc:vpc-0cf75c2e2223a751c	ok
dhcp-options:dopt-02339a53af2da8082	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace