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

Test Failures


kubetest2 Up 15m50s

exit status 1
				from junit_runner.xml

Filter through log files


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 166 lines ...
I0927 22:01:26.396951    6099 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0927 22:01:26.399199    6099 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.26.0-alpha.2+v1.26.0-alpha.1-36-gc5b8ee21f6/linux/amd64/kops
I0927 22:01:27.133027    6099 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519
I0927 22:01:27.143362    6099 up.go:44] Cleaning up any leaked resources from previous cluster
I0927 22:01:27.143493    6099 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0927 22:01:27.143543    6099 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0927 22:01:27.647686    6099 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0927 22:01:27.647738    6099 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --yes
I0927 22:01:27.647753    6099 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --yes
I0927 22:01:27.681386    6133 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io" not found
I0927 22:01:28.125391    6099 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/27 22:01:28 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
I0927 22:01:28.139023    6099 http.go:37] curl https://ip.jsb.workers.dev
I0927 22:01:28.264125    6099 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.6 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.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=containerd --admin-access 34.66.35.107/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I0927 22:01:28.264197    6099 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.6 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.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=containerd --admin-access 34.66.35.107/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I0927 22:01:28.296544    6143 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0927 22:01:28.315556    6143 create_cluster.go:846] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0927 22:01:28.842396    6143 new_cluster.go:1275]  Cloud Provider ID = aws
... skipping 574 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
W0927 22:02:14.831368    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:02:24.902536    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:02:35.393485    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:02:45.439551    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:02:55.524289    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:03:05.583492    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:03:15.641519    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:03:25.728308    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:03:35.772576    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:03:45.819049    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:03:55.868319    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:04:05.941232    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:04:15.981933    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:04:26.077134    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:04:36.153001    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:04:46.201988    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:04:56.266612    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:05:06.323376    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:05:16.376281    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:05:26.437956    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:05:36.523060    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:05:46.577543    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-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
W0927 22:05:56.667398    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 22 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is pending
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is pending
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is pending
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is pending
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is pending

Validation Failed
W0927 22:06:11.991190    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 14 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is pending
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is pending
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is pending
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is pending
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is pending

Validation Failed
W0927 22:06:25.550354    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is pending
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is pending
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is pending
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is pending
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is pending

Validation Failed
W0927 22:06:39.089092    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:06:52.598402    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:07:06.155791    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:07:19.688711    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:07:33.336926    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:07:46.872580    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:08:00.454794    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)

Validation Failed
W0927 22:08:14.039464    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)

Validation Failed
W0927 22:08:27.627286    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:08:41.197808    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:08:54.946282    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)

Validation Failed
W0927 22:09:08.563854    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)

Validation Failed
W0927 22:09:22.198044    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)

Validation Failed
W0927 22:09:35.770263    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)

Validation Failed
W0927 22:09:49.503998    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:10:03.954971    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:10:17.595526    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:10:31.266023    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:10:45.067174    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:10:58.681667    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:11:12.241792    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)

Validation Failed
W0927 22:11:25.818309    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)

Validation Failed
W0927 22:11:39.478858    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)

Validation Failed
W0927 22:11:53.101676    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:12:06.669719    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:12:20.231712    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:12:33.899477    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:12:47.424682    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:13:00.949280    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:13:14.491369    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:13:28.146997    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:13:41.702551    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:13:56.193115    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:14:09.824344    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:14:23.435845    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:14:36.984262    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5c44b6cf7d-mz6sh		system-cluster-critical pod "coredns-5c44b6cf7d-mz6sh" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)

Validation Failed
W0927 22:14:50.545743    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:15:04.185776    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:15:17.755818    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:15:31.340540    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-5b9566744f-dlfhk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-dlfhk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:15:44.950451    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:15:58.466266    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:16:12.067665    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:16:25.567727    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:16:39.232463    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:16:52.811098    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-south-1a	Master	c5.large	1	1	ap-south-1a
nodes-ap-south-1a	Node	t3.medium	4	4	ap-south-1a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9z7t7			system-node-critical pod "ebs-csi-node-9z7t7" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-b5k6g			system-node-critical pod "ebs-csi-node-b5k6g" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-m895f			system-node-critical pod "ebs-csi-node-m895f" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-tlmdp			system-node-critical pod "ebs-csi-node-tlmdp" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-z4qkb			system-node-critical pod "ebs-csi-node-z4qkb" is not ready (ebs-plugin)

Validation Failed
W0927 22:17:06.618161    6183 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0927 22:17:16.631477    6099 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0927 22:17:16.631665    6099 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0927 22:18:42.031717    6099 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0927 22:18:42.031808    6099 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0927 22:18:42.571251    6099 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0927 22:18:42.571298    6099 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/ab1bc612-3eaf-11ed-8b4c-16540f94e11e/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 303 lines ...
route-table:rtb-00acc60e674b5c476	ok
vpc:vpc-06ac069151b1d6983	ok
dhcp-options:dopt-035e5e0ba32736df5	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io

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