This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-08-21 07:18
Elapsed19m21s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 126 lines ...
I0821 07:19:27.909031    4171 up.go:43] Cleaning up any leaked resources from previous cluster
I0821 07:19:27.909079    4171 dumplogs.go:38] /logs/artifacts/db889c81-024f-11ec-8403-961c33c4a60e/kops toolbox dump --name e2e-e530783319-51438.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0821 07:19:27.946642    4191 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0821 07:19:27.946827    4191 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-e530783319-51438.test-cncf-aws.k8s.io" not found
W0821 07:19:28.556626    4171 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0821 07:19:28.556709    4171 down.go:48] /logs/artifacts/db889c81-024f-11ec-8403-961c33c4a60e/kops delete cluster --name e2e-e530783319-51438.test-cncf-aws.k8s.io --yes
I0821 07:19:28.599951    4201 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0821 07:19:28.600095    4201 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-e530783319-51438.test-cncf-aws.k8s.io" not found
I0821 07:19:29.205567    4171 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/08/21 07:19:29 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
I0821 07:19:29.215758    4171 http.go:37] curl https://ip.jsb.workers.dev
I0821 07:19:29.320184    4171 up.go:144] /logs/artifacts/db889c81-024f-11ec-8403-961c33c4a60e/kops create cluster --name e2e-e530783319-51438.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.19.14 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.3_HVM-20210209-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.123.6.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0821 07:19:29.357228    4211 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0821 07:19:29.357310    4211 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I0821 07:19:29.436685    4211 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0821 07:19:29.958289    4211 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I0821 07:19:59.661151    4171 up.go:181] /logs/artifacts/db889c81-024f-11ec-8403-961c33c4a60e/kops validate cluster --name e2e-e530783319-51438.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0821 07:19:59.677492    4232 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0821 07:19:59.677583    4232 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-e530783319-51438.test-cncf-aws.k8s.io

W0821 07:20:01.088952    4232 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e530783319-51438.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0821 07:20:11.132115    4232 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e530783319-51438.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0821 07:20:21.164034    4232 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e530783319-51438.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
W0821 07:20:31.192881    4232 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
W0821 07:20:41.237767    4232 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
W0821 07:20:51.266952    4232 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
W0821 07:21:01.310922    4232 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
W0821 07:21:11.348006    4232 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
W0821 07:21:21.384227    4232 validate_cluster.go:221] (will retry): cluster not yet healthy
W0821 07:21:31.422932    4232 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e530783319-51438.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
W0821 07:21:41.454504    4232 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
W0821 07:21:51.497835    4232 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
W0821 07:22:01.546000    4232 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
W0821 07:22:11.579814    4232 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
W0821 07:22:21.609745    4232 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
W0821 07:22:31.639853    4232 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
W0821 07:22:41.676649    4232 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
W0821 07:22:51.710403    4232 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
W0821 07:23:01.741963    4232 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
W0821 07:23:11.774169    4232 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
W0821 07:23:21.834746    4232 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
W0821 07:23:31.869063    4232 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
W0821 07:23:41.900788    4232 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
W0821 07:23:51.929376    4232 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
W0821 07:24:01.959484    4232 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
W0821 07:24:12.007610    4232 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
W0821 07:24:22.038608    4232 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
W0821 07:24:32.072408    4232 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
W0821 07:24:42.110854    4232 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
W0821 07:24:52.159183    4232 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
W0821 07:25:02.227339    4232 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
W0821 07:25:12.263289    4232 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
W0821 07:25:22.292475    4232 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
W0821 07:25:32.327172    4232 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
W0821 07:25:42.357078    4232 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
W0821 07:25:52.384534    4232 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
W0821 07:26:02.420406    4232 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
W0821 07:26:12.466908    4232 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
W0821 07:26:22.507550    4232 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
W0821 07:26:32.550830    4232 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
W0821 07:26:42.595500    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:26:56.327689    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:27:09.213625    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:27:21.542676    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:27:33.932825    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:27:46.362697    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:27:58.824859    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:28:11.231626    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:28:23.675561    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:28:36.037555    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:28:48.365341    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:29:00.719984    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:29:13.145479    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:29:25.557628    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:29:38.031491    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:29:50.440033    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:30:02.908834    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:30:15.322002    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:30:27.869698    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:30:40.264089    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:30:53.193883    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:31:05.591124    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:31:18.180176    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:31:30.663739    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:31:43.054478    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:31:55.503629    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:32:08.327875    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:32:20.885845    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:32:33.320644    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:32:45.760322    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:32:58.508808    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:33:10.859104    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:33:23.273466    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:33:35.689501    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:33:48.018576    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:34:00.368426    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:34:12.778396    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:34:25.276822    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:34:37.666952    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:34:50.638976    4232 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-0e463fe34d0edb0eb					machine "i-0e463fe34d0edb0eb" has not yet joined cluster
Node	ip-172-20-49-58.sa-east-1.compute.internal		node "ip-172-20-49-58.sa-east-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-gq492				system-node-critical pod "cilium-gq492" is pending
Pod	kube-system/kube-dns-696cb84c7-5kjxw			system-cluster-critical pod "kube-dns-696cb84c7-5kjxw" is pending
Pod	kube-system/kube-dns-autoscaler-55f8f75459-58ddw	system-cluster-critical pod "kube-dns-autoscaler-55f8f75459-58ddw" is pending

Validation Failed
W0821 07:35:03.163309    4232 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0821 07:35:13.172785    4171 dumplogs.go:38] /logs/artifacts/db889c81-024f-11ec-8403-961c33c4a60e/kops toolbox dump --name e2e-e530783319-51438.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0821 07:35:13.192052    4243 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I0821 07:35:13.192322    4243 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/08/21 07:35:25 Dumping node ip-172-20-49-58.sa-east-1.compute.internal
2021/08/21 07:35:32 dumping node not registered in kubernetes: 18.231.113.124
2021/08/21 07:35:32 Dumping node 18.231.113.124
... skipping 1195 lines ...
route-table:rtb-0469363d58c04f593	ok
vpc:vpc-08e53153e956cb770	ok
dhcp-options:dopt-0a516f6bc4ab358c6	ok
Deleted kubectl config for e2e-e530783319-51438.test-cncf-aws.k8s.io

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