This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-01 21:39
Elapsed20m34s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1001 21:40:54.493965    4759 up.go:43] Cleaning up any leaked resources from previous cluster
I1001 21:40:54.493999    4759 dumplogs.go:40] /logs/artifacts/06e7bf90-2300-11ec-b24b-7a6e88b2f90d/kops toolbox dump --name e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1001 21:40:54.509689    4777 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1001 21:40:54.509786    4777 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io" not found
W1001 21:40:55.034198    4759 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1001 21:40:55.034378    4759 down.go:48] /logs/artifacts/06e7bf90-2300-11ec-b24b-7a6e88b2f90d/kops delete cluster --name e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io --yes
I1001 21:40:55.051444    4787 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1001 21:40:55.051596    4787 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io" not found
I1001 21:40:55.571164    4759 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/01 21:40:55 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
I1001 21:40:55.580335    4759 http.go:37] curl https://ip.jsb.workers.dev
I1001 21:40:55.739347    4759 up.go:144] /logs/artifacts/06e7bf90-2300-11ec-b24b-7a6e88b2f90d/kops create cluster --name e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.2.0_HVM-20210907-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=containerd --admin-access 34.121.253.144/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I1001 21:40:55.754706    4796 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1001 21:40:55.754802    4796 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1001 21:40:55.809026    4796 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1001 21:40:56.551651    4796 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 41 lines ...

I1001 21:41:18.868585    4759 up.go:181] /logs/artifacts/06e7bf90-2300-11ec-b24b-7a6e88b2f90d/kops validate cluster --name e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1001 21:41:18.885569    4815 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1001 21:41:18.885696    4815 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io

W1001 21:41:20.789800    4815 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1001 21:41:30.831286    4815 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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
W1001 21:41:40.878741    4815 validate_cluster.go:221] (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
W1001 21:41:50.935491    4815 validate_cluster.go:221] (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
W1001 21:42:01.008938    4815 validate_cluster.go:221] (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
W1001 21:42:11.048921    4815 validate_cluster.go:221] (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
W1001 21:42:21.106564    4815 validate_cluster.go:221] (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
W1001 21:42:31.152866    4815 validate_cluster.go:221] (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
W1001 21:42:41.211647    4815 validate_cluster.go:221] (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
W1001 21:42:51.255185    4815 validate_cluster.go:221] (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
W1001 21:43:01.297497    4815 validate_cluster.go:221] (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
W1001 21:43:11.342663    4815 validate_cluster.go:221] (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
W1001 21:43:21.389974    4815 validate_cluster.go:221] (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
W1001 21:43:31.430677    4815 validate_cluster.go:221] (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
W1001 21:43:41.476857    4815 validate_cluster.go:221] (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
W1001 21:43:51.522388    4815 validate_cluster.go:221] (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
W1001 21:44:01.577275    4815 validate_cluster.go:221] (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
W1001 21:44:11.620228    4815 validate_cluster.go:221] (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
W1001 21:44:21.678985    4815 validate_cluster.go:221] (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
W1001 21:44:31.717553    4815 validate_cluster.go:221] (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
W1001 21:44:41.758194    4815 validate_cluster.go:221] (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
W1001 21:44:51.796289    4815 validate_cluster.go:221] (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
W1001 21:45:01.841003    4815 validate_cluster.go:221] (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
W1001 21:45:11.898268    4815 validate_cluster.go:221] (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
W1001 21:45:21.944011    4815 validate_cluster.go:221] (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
W1001 21:45:31.989996    4815 validate_cluster.go:221] (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
W1001 21:45:42.037270    4815 validate_cluster.go:221] (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
W1001 21:45:52.094558    4815 validate_cluster.go:221] (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
W1001 21:46:02.151016    4815 validate_cluster.go:221] (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
W1001 21:46:12.209961    4815 validate_cluster.go:221] (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
W1001 21:46:22.269129    4815 validate_cluster.go:221] (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
W1001 21:46:32.313912    4815 validate_cluster.go:221] (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
W1001 21:46:42.355086    4815 validate_cluster.go:221] (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
W1001 21:46:52.396871    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:47:08.108091    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:47:21.827727    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:47:35.551109    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:47:49.308274    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:48:02.989928    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:48:16.716763    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:48:30.474269    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:48:44.237701    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:48:58.019285    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:49:11.795742    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:49:25.514949    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:49:39.151638    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:49:52.986210    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:50:06.635271    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:50:20.349290    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:50:33.997949    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:50:47.708299    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:51:02.319110    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:51:16.215254    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:51:30.038367    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:51:43.857203    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:51:57.664578    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:52:11.500973    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:52:25.401281    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:52:39.292634    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:52:53.122866    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:53:06.965506    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:53:20.777892    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:53:34.550477    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:53:48.362733    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:54:02.277363    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:54:16.028363    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:54:29.822149    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:54:43.583007    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:54:58.131182    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:55:11.902914    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:55:25.732656    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:55:39.500547    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:55:53.291401    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:56:07.087602    4815 validate_cluster.go:221] (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 ...
Machine	i-0e3dfef003734aeba				machine "i-0e3dfef003734aeba" has not yet joined cluster
Node	ip-172-20-57-106.ap-south-1.compute.internal	node "ip-172-20-57-106.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x9xlh			system-node-critical pod "cilium-x9xlh" is pending
Pod	kube-system/coredns-5dc785954d-27p6l		system-cluster-critical pod "coredns-5dc785954d-27p6l" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-bsx56	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-bsx56" is pending

Validation Failed
W1001 21:56:20.907020    4815 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1001 21:56:30.916247    4759 dumplogs.go:40] /logs/artifacts/06e7bf90-2300-11ec-b24b-7a6e88b2f90d/kops toolbox dump --name e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1001 21:56:30.935245    4828 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1001 21:56:30.935369    4828 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/01 21:56:47 Dumping node ip-172-20-57-106.ap-south-1.compute.internal
2021/10/01 21:56:58 dumping node not registered in kubernetes: 13.234.112.231
2021/10/01 21:56:58 Dumping node 13.234.112.231
... skipping 1301 lines ...
route-table:rtb-0d8aa4dbeb1af1b60	ok
vpc:vpc-0f56578acc71a295f	ok
dhcp-options:dopt-07defa05e961b719f	ok
Deleted kubectl config for e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io

Deleted cluster: "e2e-d0469869f2-8ebdc.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace