This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-23 03:52
Elapsed18m8s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 132 lines ...
I0923 03:53:30.203330    4652 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0923 03:53:30.204816    4652 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.23.0-alpha.2+v1.23.0-alpha.1-234-gdefcdedb68/linux/amd64/kops
I0923 03:53:31.046272    4652 up.go:43] Cleaning up any leaked resources from previous cluster
I0923 03:53:31.046308    4652 dumplogs.go:40] /logs/artifacts/9f9c4f87-1c21-11ec-883b-c61df66c07e7/kops toolbox dump --name e2e-42d564571f-cfa81.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0923 03:53:31.062051    4671 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 03:53:31.062159    4671 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-42d564571f-cfa81.test-cncf-aws.k8s.io" not found
W0923 03:53:31.542678    4652 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0923 03:53:31.542767    4652 down.go:48] /logs/artifacts/9f9c4f87-1c21-11ec-883b-c61df66c07e7/kops delete cluster --name e2e-42d564571f-cfa81.test-cncf-aws.k8s.io --yes
I0923 03:53:31.560330    4681 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 03:53:31.560453    4681 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-42d564571f-cfa81.test-cncf-aws.k8s.io" not found
I0923 03:53:32.034723    4652 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/23 03:53:32 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
I0923 03:53:32.049213    4652 http.go:37] curl https://ip.jsb.workers.dev
I0923 03:53:32.140952    4652 up.go:144] /logs/artifacts/9f9c4f87-1c21-11ec-883b-c61df66c07e7/kops create cluster --name e2e-42d564571f-cfa81.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.2.0_HVM-20210907-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.121.191.223/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0923 03:53:32.158714    4691 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 03:53:32.159381    4691 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0923 03:53:32.180691    4691 create_cluster.go:839] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0923 03:53:32.655554    4691 new_cluster.go:1074]  Cloud Provider ID = aws
... skipping 46 lines ...

I0923 03:54:01.426741    4652 up.go:181] /logs/artifacts/9f9c4f87-1c21-11ec-883b-c61df66c07e7/kops validate cluster --name e2e-42d564571f-cfa81.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0923 03:54:01.444998    4711 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 03:54:01.445092    4711 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-42d564571f-cfa81.test-cncf-aws.k8s.io

W0923 03:54:03.017578    4711 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-42d564571f-cfa81.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
W0923 03:54:13.051552    4711 validate_cluster.go:232] (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
W0923 03:54:23.083482    4711 validate_cluster.go:232] (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
W0923 03:54:33.112919    4711 validate_cluster.go:232] (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
W0923 03:54:43.178360    4711 validate_cluster.go:232] (will retry): cluster not yet healthy
W0923 03:54:53.570212    4711 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-42d564571f-cfa81.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
W0923 03:55:03.602032    4711 validate_cluster.go:232] (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
W0923 03:55:13.636925    4711 validate_cluster.go:232] (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
W0923 03:55:23.679652    4711 validate_cluster.go:232] (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
W0923 03:55:33.728608    4711 validate_cluster.go:232] (will retry): cluster not yet healthy
W0923 03:55:43.750708    4711 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-42d564571f-cfa81.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
W0923 03:55:53.805813    4711 validate_cluster.go:232] (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
W0923 03:56:03.840062    4711 validate_cluster.go:232] (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
W0923 03:56:13.869334    4711 validate_cluster.go:232] (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
W0923 03:56:24.057933    4711 validate_cluster.go:232] (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
W0923 03:56:34.092526    4711 validate_cluster.go:232] (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
W0923 03:56:44.125535    4711 validate_cluster.go:232] (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
W0923 03:56:54.166571    4711 validate_cluster.go:232] (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
W0923 03:57:04.205076    4711 validate_cluster.go:232] (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
W0923 03:57:14.238181    4711 validate_cluster.go:232] (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
W0923 03:57:24.384379    4711 validate_cluster.go:232] (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
W0923 03:57:34.415730    4711 validate_cluster.go:232] (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
W0923 03:57:44.463560    4711 validate_cluster.go:232] (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
W0923 03:57:54.499964    4711 validate_cluster.go:232] (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
W0923 03:58:04.547298    4711 validate_cluster.go:232] (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
W0923 03:58:14.579719    4711 validate_cluster.go:232] (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
W0923 03:58:24.622983    4711 validate_cluster.go:232] (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
W0923 03:58:34.662274    4711 validate_cluster.go:232] (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
W0923 03:58:44.697430    4711 validate_cluster.go:232] (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
W0923 03:58:54.743706    4711 validate_cluster.go:232] (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
W0923 03:59:04.787551    4711 validate_cluster.go:232] (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 12 lines ...
Pod	kube-system/cilium-86gh2							system-node-critical pod "cilium-86gh2" is pending
Pod	kube-system/cilium-k6vkq							system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl						system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z					system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending
Pod	kube-system/etcd-manager-events-ip-172-20-42-112.sa-east-1.compute.internal	system-cluster-critical pod "etcd-manager-events-ip-172-20-42-112.sa-east-1.compute.internal" is pending

Validation Failed
W0923 03:59:18.557710    4711 validate_cluster.go:232] (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 11 lines ...
Node	ip-172-20-57-179.sa-east-1.compute.internal	node "ip-172-20-57-179.sa-east-1.compute.internal" of role "node" is not ready
Pod	kube-system/cilium-86gh2			system-node-critical pod "cilium-86gh2" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 03:59:31.183845    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 03:59:43.594322    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 03:59:56.076118    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:00:08.516856    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:00:20.935347    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:00:33.337650    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:00:45.709304    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:00:58.121726    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:01:10.545583    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:01:22.978416    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:01:35.570504    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:01:48.071691    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:02:00.627120    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:02:13.003041    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:02:25.447021    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:02:38.405582    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:02:50.865325    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:03:03.391621    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:03:16.404327    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:03:29.028524    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:03:41.405222    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:03:53.864335    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:04:06.234011    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:04:18.630240    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:04:31.014304    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:04:43.602581    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:04:56.098364    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:05:09.184470    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:05:21.705752    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:05:34.174945    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:05:46.594913    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:05:58.998107    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:06:11.476232    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:06:24.213404    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:06:36.586389    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:06:48.910072    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:07:01.305704    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:07:14.248240    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:07:26.729295    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:07:39.128830    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:07:51.569226    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:08:05.066484    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:08:17.453498    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:08:29.863695    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:08:42.330804    4711 validate_cluster.go:232] (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 17 lines ...
Pod	kube-system/cilium-j9zw6			system-node-critical pod "cilium-j9zw6" is pending
Pod	kube-system/cilium-k6vkq			system-node-critical pod "cilium-k6vkq" is pending
Pod	kube-system/cilium-q7tkw			system-node-critical pod "cilium-q7tkw" is pending
Pod	kube-system/coredns-5dc785954d-f2bzl		system-cluster-critical pod "coredns-5dc785954d-f2bzl" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-n6n8z	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-n6n8z" is pending

Validation Failed
W0923 04:08:54.743351    4711 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0923 04:09:04.749106    4652 dumplogs.go:40] /logs/artifacts/9f9c4f87-1c21-11ec-883b-c61df66c07e7/kops toolbox dump --name e2e-42d564571f-cfa81.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0923 04:09:04.769854    4722 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0923 04:09:04.770000    4722 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/23 04:09:16 Dumping node ip-172-20-42-112.sa-east-1.compute.internal
2021/09/23 04:09:25 Dumping node ip-172-20-46-143.sa-east-1.compute.internal
2021/09/23 04:09:30 Dumping node ip-172-20-53-89.sa-east-1.compute.internal
... skipping 1167 lines ...
route-table:rtb-00011f043d57eacb6	ok
vpc:vpc-09b4d6a0ce3b9b758	ok
dhcp-options:dopt-0c6f12277f520b16d	ok
Deleted kubectl config for e2e-42d564571f-cfa81.test-cncf-aws.k8s.io

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