This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-07 12:03
Elapsed18m32s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1007 12:03:54.419038    4687 up.go:43] Cleaning up any leaked resources from previous cluster
I1007 12:03:54.419105    4687 dumplogs.go:40] /logs/artifacts/73e6af5d-2766-11ec-8be6-fe96b6157dda/kops toolbox dump --name e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1007 12:03:54.436182    4705 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1007 12:03:54.436328    4705 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io" not found
W1007 12:03:54.981900    4687 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1007 12:03:54.981983    4687 down.go:48] /logs/artifacts/73e6af5d-2766-11ec-8be6-fe96b6157dda/kops delete cluster --name e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io --yes
I1007 12:03:54.996723    4715 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1007 12:03:54.996814    4715 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io" not found
I1007 12:03:55.533418    4687 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/07 12:03: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
I1007 12:03:55.541472    4687 http.go:37] curl https://ip.jsb.workers.dev
I1007 12:03:55.640198    4687 up.go:144] /logs/artifacts/73e6af5d-2766-11ec-8be6-fe96b6157dda/kops create cluster --name e2e-0fd86baae9-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 35.225.211.47/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I1007 12:03:55.655468    4724 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1007 12:03:55.655565    4724 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1007 12:03:55.699436    4724 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1007 12:03:56.202258    4724 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1007 12:04:25.065871    4687 up.go:181] /logs/artifacts/73e6af5d-2766-11ec-8be6-fe96b6157dda/kops validate cluster --name e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1007 12:04:25.080850    4744 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1007 12:04:25.080948    4744 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io

W1007 12:04:26.579320    4744 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:04:36.612435    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:04:46.645078    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:04:56.676254    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:05:06.715807    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:05:16.746122    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:05:26.810337    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:05:36.841810    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:05:46.904470    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:05:56.938919    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:06:07.147683    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:06:17.355407    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:06:27.418859    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:06:37.458098    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:06:47.497231    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:06:57.535053    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:07:07.572956    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:07:18.033236    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:07:28.065115    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:07:38.097550    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:07:48.133283    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:07:58.172358    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:08:08.205665    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:08:18.245620    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:08:28.278210    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:08:38.316357    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:08:48.351989    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:08:58.386001    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:09:08.436309    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:09:18.468881    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:09:28.498654    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:09:38.529925    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:09:48.563775    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:09:58.594508    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:10:08.629243    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-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
W1007 12:10:18.673793    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:10:32.213754    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:10:44.983635    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:10:57.450252    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:11:09.895968    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:11:22.364010    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:11:34.819823    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:11:47.291934    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:11:59.771947    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:12:12.235351    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:12:24.728485    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:12:37.080011    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:12:49.540870    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:13:02.028812    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:13:14.594530    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:13:27.105609    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:13:39.571102    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:13:52.015593    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:14:04.473940    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:14:17.025598    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:14:29.943311    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:14:42.383523    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:14:54.849721    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:15:07.317542    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:15:19.915180    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:15:32.368450    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:15:44.889472    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:15:57.414693    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:16:09.798368    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:16:22.202818    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:16:34.647861    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:16:47.064920    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:16:59.547154    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:17:11.916650    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:17:24.391946    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:17:36.843387    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:17:49.455041    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:18:01.836234    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:18:14.358708    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:18:27.247314    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:18:39.860940    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:18:52.273267    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:19:04.712392    4744 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-sa-east-1a	Master	c5.large	1	1	sa-east-1a
nodes-sa-east-1a	Node	t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0f5409952a838638f				machine "i-0f5409952a838638f" has not yet joined cluster
Node	ip-172-20-61-160.sa-east-1.compute.internal	node "ip-172-20-61-160.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-wpnf9			system-node-critical pod "cilium-wpnf9" is pending
Pod	kube-system/coredns-64497985bd-j7n5d		system-cluster-critical pod "coredns-64497985bd-j7n5d" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jc7vp	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jc7vp" is pending

Validation Failed
W1007 12:19:17.175137    4744 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1007 12:19:27.184900    4687 dumplogs.go:40] /logs/artifacts/73e6af5d-2766-11ec-8be6-fe96b6157dda/kops toolbox dump --name e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1007 12:19:27.201583    4755 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1007 12:19:27.201689    4755 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/07 12:19:38 Dumping node ip-172-20-61-160.sa-east-1.compute.internal
2021/10/07 12:19:45 dumping node not registered in kubernetes: 54.233.96.220
2021/10/07 12:19:45 Dumping node 54.233.96.220
... skipping 1187 lines ...
route-table:rtb-091ec1b9fbef4960d	ok
vpc:vpc-024cd7bbbe836fd08	ok
dhcp-options:dopt-058feb78507939d32	ok
Deleted kubectl config for e2e-0fd86baae9-773a8.test-cncf-aws.k8s.io

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