This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-16 12:02
Elapsed19m12s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0916 12:03:47.096246    4094 up.go:43] Cleaning up any leaked resources from previous cluster
I0916 12:03:47.096324    4094 dumplogs.go:38] /logs/artifacts/e71ef937-16e5-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0916 12:03:47.130129    4112 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0916 12:03:47.130270    4112 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io" not found
W0916 12:03:47.742397    4094 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0916 12:03:47.742475    4094 down.go:48] /logs/artifacts/e71ef937-16e5-11ec-a0c8-aafcb65c973d/kops delete cluster --name e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io --yes
I0916 12:03:47.767071    4123 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0916 12:03:47.767399    4123 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io" not found
I0916 12:03:48.369167    4094 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/16 12:03:48 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0916 12:03:48.378148    4094 http.go:37] curl https://ip.jsb.workers.dev
I0916 12:03:48.472031    4094 up.go:144] /logs/artifacts/e71ef937-16e5-11ec-a0c8-aafcb65c973d/kops create cluster --name e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.134.22.252/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-south-1a --master-size c5.large
I0916 12:03:48.499119    4134 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0916 12:03:48.499266    4134 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0916 12:03:48.609358    4134 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0916 12:03:49.168422    4134 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 46 lines ...

I0916 12:04:12.340204    4094 up.go:181] /logs/artifacts/e71ef937-16e5-11ec-a0c8-aafcb65c973d/kops validate cluster --name e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0916 12:04:12.367087    4155 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0916 12:04:12.367324    4155 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io

W0916 12:04:14.279237    4155 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0916 12:04:24.315368    4155 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-581bb0bf23-773a8.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
W0916 12:04:34.350887    4155 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
W0916 12:04:44.411009    4155 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
W0916 12:04:54.454801    4155 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
W0916 12:05:04.486384    4155 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
W0916 12:05:14.528721    4155 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
W0916 12:05:24.559179    4155 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
W0916 12:05:34.588967    4155 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
W0916 12:05:44.629913    4155 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
W0916 12:05:54.658816    4155 validate_cluster.go:221] (will retry): cluster not yet healthy
W0916 12:06:04.678547    4155 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-581bb0bf23-773a8.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
W0916 12:06:14.844314    4155 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
W0916 12:06:24.909810    4155 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
W0916 12:06:34.940619    4155 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
W0916 12:06:45.095294    4155 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
W0916 12:06:55.190248    4155 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
W0916 12:07:05.426109    4155 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
W0916 12:07:15.471713    4155 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
W0916 12:07:25.505474    4155 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
W0916 12:07:35.547868    4155 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
W0916 12:07:45.582822    4155 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
W0916 12:07:55.651031    4155 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
W0916 12:08:05.694764    4155 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
W0916 12:08:15.747358    4155 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
W0916 12:08:25.898041    4155 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
W0916 12:08:35.938235    4155 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
W0916 12:08:45.979503    4155 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
W0916 12:08:56.017590    4155 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
W0916 12:09:06.046529    4155 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
W0916 12:09:16.096957    4155 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
W0916 12:09:26.126621    4155 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
W0916 12:09:36.158101    4155 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
W0916 12:09:46.193983    4155 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
W0916 12:09:56.227925    4155 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
W0916 12:10:06.262800    4155 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
W0916 12:10:16.294305    4155 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 10 lines ...
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/cilium-operator-54c867bdf7-cr2nf	system-cluster-critical pod "cilium-operator-54c867bdf7-cr2nf" is not ready (cilium-operator)
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:10:32.156711    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:10:45.969904    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:10:59.857107    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:11:13.761285    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:11:27.401216    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:11:41.210987    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:11:54.922471    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:12:08.682203    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:12:22.443356    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:12:36.165540    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:12:49.948737    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:13:03.630151    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:13:17.281171    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:13:31.021734    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:13:44.687131    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:13:58.288210    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:14:12.131113    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:14:26.626832    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:14:40.345468    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:14:53.923994    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:15:07.575478    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:15:21.256081    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:15:34.992958    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:15:48.770108    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:16:02.473566    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:16:16.072845    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:16:29.818397    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:16:43.491378    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:16:57.107964    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:17:10.850737    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:17:24.649060    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:17:38.263037    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:17:51.918080    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:18:05.577552    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:18:20.323773    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:18:33.949492    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:18:47.602568    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:19:01.306483    4155 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-078f55a684f5a727c				machine "i-078f55a684f5a727c" has not yet joined cluster
Node	ip-172-20-45-207.ap-south-1.compute.internal	node "ip-172-20-45-207.ap-south-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-m8dpw			system-node-critical pod "cilium-m8dpw" is pending
Pod	kube-system/coredns-64497985bd-qjwgc		system-cluster-critical pod "coredns-64497985bd-qjwgc" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-lzlj6	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-lzlj6" is pending

Validation Failed
W0916 12:19:15.110545    4155 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0916 12:19:25.126906    4094 dumplogs.go:38] /logs/artifacts/e71ef937-16e5-11ec-a0c8-aafcb65c973d/kops toolbox dump --name e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0916 12:19:25.149883    4165 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0916 12:19:25.150043    4165 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/09/16 12:19:40 Dumping node ip-172-20-45-207.ap-south-1.compute.internal
2021/09/16 12:19:52 dumping node not registered in kubernetes: 65.2.149.88
2021/09/16 12:19:52 Dumping node 65.2.149.88
... skipping 1199 lines ...
route-table:rtb-051e4406b3d1167c5	ok
vpc:vpc-0eb34075f85e0de8a	ok
dhcp-options:dopt-074fbde0f154f04ce	ok
Deleted kubectl config for e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io

Deleted cluster: "e2e-581bb0bf23-773a8.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace