This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-18 18:38
Elapsed21m10s
Revisionmaster

Test Failures


kubetest2 Up 15m59s

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 159 lines ...
I0718 18:39:52.622570    5982 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0718 18:39:52.625037    5982 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-91-g13f936a02c/linux/amd64/kops
I0718 18:39:53.380177    5982 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519
I0718 18:39:53.388712    5982 up.go:44] Cleaning up any leaked resources from previous cluster
I0718 18:39:53.388808    5982 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops toolbox dump --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0718 18:39:53.388831    5982 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops toolbox dump --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
W0718 18:39:53.889930    5982 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0718 18:39:53.889980    5982 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops delete cluster --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --yes
I0718 18:39:53.889992    5982 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops delete cluster --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --yes
I0718 18:39:53.909859    6015 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io" not found
I0718 18:39:54.403647    5982 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/18 18:39:54 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
I0718 18:39:54.413863    5982 http.go:37] curl https://ip.jsb.workers.dev
I0718 18:39:54.582801    5982 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops create cluster --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.5.0_HVM-20211103-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 35.188.137.78/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I0718 18:39:54.582841    5982 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops create cluster --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.5.0_HVM-20211103-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 35.188.137.78/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I0718 18:39:54.603429    6025 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0718 18:39:54.630755    6025 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0718 18:39:55.250229    6025 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 535 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
W0718 18:40:51.953625    6060 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
W0718 18:41:01.989860    6060 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
W0718 18:41:12.032201    6060 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
W0718 18:41:22.074002    6060 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
W0718 18:41:32.129816    6060 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
W0718 18:41:42.173866    6060 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
W0718 18:41:52.224030    6060 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
W0718 18:42:02.267263    6060 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
W0718 18:42:12.307355    6060 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
W0718 18:42:22.346785    6060 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
W0718 18:42:32.386386    6060 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
W0718 18:42:42.452959    6060 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
W0718 18:42:52.489612    6060 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
W0718 18:43:02.533764    6060 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
W0718 18:43:12.582181    6060 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
W0718 18:43:22.619837    6060 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
W0718 18:43:32.660934    6060 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
W0718 18:43:42.701892    6060 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
W0718 18:43:52.741465    6060 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
W0718 18:44:02.776026    6060 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
W0718 18:44:12.822696    6060 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
W0718 18:44:22.860431    6060 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
W0718 18:44:32.897654    6060 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
W0718 18:44:42.987329    6060 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
W0718 18:44:53.026730    6060 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
W0718 18:45:03.067223    6060 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
W0718 18:45:13.111623    6060 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
W0718 18:45:23.150359    6060 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
W0718 18:45:33.185882    6060 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
W0718 18:45:43.237071    6060 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
W0718 18:45:53.285456    6060 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
W0718 18:46:03.319967    6060 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
W0718 18:46:13.368348    6060 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 ...
Machine	i-0b5b5f17d69dc5ed2					machine "i-0b5b5f17d69dc5ed2" has not yet joined cluster
Machine	i-0e9d5a7703edab87e					machine "i-0e9d5a7703edab87e" has not yet joined cluster
Node	ip-172-20-47-109.ap-south-1.compute.internal		node "ip-172-20-47-109.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/calico-kube-controllers-7455d7799b-knngw	system-cluster-critical pod "calico-kube-controllers-7455d7799b-knngw" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending

Validation Failed
W0718 18:46:29.294447    6060 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 16 lines ...
Pod	kube-system/calico-node-5549b				system-node-critical pod "calico-node-5549b" is pending
Pod	kube-system/calico-node-jnslg				system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending

Validation Failed
W0718 18:46:43.004166    6060 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 16 lines ...
Pod	kube-system/calico-node-5549b				system-node-critical pod "calico-node-5549b" is pending
Pod	kube-system/calico-node-jnslg				system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending

Validation Failed
W0718 18:46:56.784371    6060 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 16 lines ...
Pod	kube-system/calico-node-5549b				system-node-critical pod "calico-node-5549b" is pending
Pod	kube-system/calico-node-jnslg				system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending

Validation Failed
W0718 18:47:10.846760    6060 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 16 lines ...
Pod	kube-system/calico-node-5549b				system-node-critical pod "calico-node-5549b" is pending
Pod	kube-system/calico-node-jnslg				system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending

Validation Failed
W0718 18:47:24.608942    6060 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 17 lines ...
Pod	kube-system/calico-node-jnslg						system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs						system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8						system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7						system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-106.ap-south-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-106.ap-south-1.compute.internal" is pending

Validation Failed
W0718 18:47:38.343080    6060 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 16 lines ...
Pod	kube-system/calico-node-5549b				system-node-critical pod "calico-node-5549b" is pending
Pod	kube-system/calico-node-jnslg				system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending

Validation Failed
W0718 18:47:52.183131    6060 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 16 lines ...
Pod	kube-system/calico-node-5549b				system-node-critical pod "calico-node-5549b" is pending
Pod	kube-system/calico-node-jnslg				system-node-critical pod "calico-node-jnslg" is pending
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending

Validation Failed
W0718 18:48:05.938333    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:48:19.579491    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:48:33.299021    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:48:47.097193    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:49:00.830544    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:49:14.699424    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:49:28.505510    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:49:42.379027    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:49:56.503034    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:50:10.507258    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:50:25.034965    6060 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 18 lines ...
Pod	kube-system/calico-node-lcdqs				system-node-critical pod "calico-node-lcdqs" is pending
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending

Validation Failed
W0718 18:50:38.764823    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:50:52.490773    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:51:06.185576    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:51:19.826190    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:51:33.427848    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:51:47.183502    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:52:00.978144    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:52:14.788240    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:52:28.427424    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:52:42.251068    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:52:55.983769    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:53:09.709581    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:53:23.373728    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:53:37.106817    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:53:50.828246    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:54:04.550957    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:54:19.205195    6060 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 19 lines ...
Pod	kube-system/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is pending
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is pending
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:54:33.024054    6060 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/calico-node-mwcr8				system-node-critical pod "calico-node-mwcr8" is not ready (calico-node)
Pod	kube-system/calico-node-zc5h7				system-node-critical pod "calico-node-zc5h7" is not ready (calico-node)
Pod	kube-system/coredns-5fcc7b6498-6k59m			system-cluster-critical pod "coredns-5fcc7b6498-6k59m" is pending
Pod	kube-system/coredns-autoscaler-6658b4bf85-cqpw4		system-cluster-critical pod "coredns-autoscaler-6658b4bf85-cqpw4" is pending
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj		system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:54:46.902601    6060 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/calico-node-jnslg			system-node-critical pod "calico-node-jnslg" is not ready (calico-node)
Pod	kube-system/ebs-csi-controller-6dc4cf9457-9xzlj	system-cluster-critical pod "ebs-csi-controller-6dc4cf9457-9xzlj" is pending

Validation Failed
W0718 18:55:00.788154    6060 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 34 lines ...
ip-172-20-50-139.ap-south-1.compute.internal	node	True
ip-172-20-53-44.ap-south-1.compute.internal	node	True
ip-172-20-61-106.ap-south-1.compute.internal	node	True

Your cluster e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io is ready
I0718 18:55:42.300757    6060 validate_cluster.go:220] (will retry): cluster passed validation 3 consecutive times
Error: Validation failed: wait time exceeded during validation
I0718 18:55:52.306992    5982 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops toolbox dump --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0718 18:55:52.307116    5982 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops toolbox dump --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0718 18:57:09.932504    5982 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops get cluster --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0718 18:57:09.932623    5982 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops get cluster --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0718 18:57:10.421942    5982 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops get instancegroups --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0718 18:57:10.421979    5982 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c98c68fa-06c8-11ed-8efc-ce24b6ad9583/kops get instancegroups --name e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 309 lines ...
route-table:rtb-06e6a4af68b66ff55	ok
vpc:vpc-02569f72d531632af	ok
dhcp-options:dopt-0184577c45159a3e4	ok
Deleted kubectl config for e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-calico-rhel8-k22-containerd.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace