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

No Test Failures!


Error lines from build-log.txt

... skipping 128 lines ...
I1012 08:41:01.257076    4710 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I1012 08:41:01.258704    4710 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.3+v1.22.0-beta.2-34-gab6c4fd5b0/linux/amd64/kops
I1012 08:41:02.137685    4710 up.go:43] Cleaning up any leaked resources from previous cluster
I1012 08:41:02.137718    4710 dumplogs.go:40] /logs/artifacts/ed6138e9-2b37-11ec-94fd-caf12f285ed9/kops toolbox dump --name e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1012 08:41:02.157187    4731 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 08:41:02.157295    4731 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io" not found
W1012 08:41:02.656421    4710 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1012 08:41:02.656468    4710 down.go:48] /logs/artifacts/ed6138e9-2b37-11ec-94fd-caf12f285ed9/kops delete cluster --name e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io --yes
I1012 08:41:02.674056    4741 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 08:41:02.674158    4741 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io" not found
I1012 08:41:03.196402    4710 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/12 08:41:03 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
I1012 08:41:03.203776    4710 http.go:37] curl https://ip.jsb.workers.dev
I1012 08:41:03.286346    4710 up.go:144] /logs/artifacts/ed6138e9-2b37-11ec-94fd-caf12f285ed9/kops create cluster --name e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=docker --admin-access 35.202.185.108/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I1012 08:41:03.304495    4751 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 08:41:03.304606    4751 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I1012 08:41:03.330280    4751 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1012 08:41:04.051967    4751 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 41 lines ...

I1012 08:41:32.507387    4710 up.go:181] /logs/artifacts/ed6138e9-2b37-11ec-94fd-caf12f285ed9/kops validate cluster --name e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1012 08:41:32.524677    4771 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 08:41:32.524803    4771 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io

W1012 08:41:33.951938    4771 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f30ae0f9-ec357.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
W1012 08:41:44.012771    4771 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
W1012 08:41:54.068851    4771 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
W1012 08:42:04.098875    4771 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
W1012 08:42:14.134283    4771 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
W1012 08:42:24.165737    4771 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
W1012 08:42:34.194280    4771 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
W1012 08:42:44.231842    4771 validate_cluster.go:232] (will retry): cluster not yet healthy
W1012 08:42:54.262287    4771 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b6f30ae0f9-ec357.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
W1012 08:43:04.296094    4771 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
W1012 08:43:14.332000    4771 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
W1012 08:43:24.369774    4771 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
W1012 08:43:34.402993    4771 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
W1012 08:43:44.469804    4771 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
W1012 08:43:54.515203    4771 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
W1012 08:44:04.544528    4771 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
W1012 08:44:14.580361    4771 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
W1012 08:44:24.640730    4771 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
W1012 08:44:34.678790    4771 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
W1012 08:44:44.716469    4771 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
W1012 08:44:54.755128    4771 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
W1012 08:45:04.789589    4771 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
W1012 08:45:14.824188    4771 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
W1012 08:45:24.854884    4771 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
W1012 08:45:34.884758    4771 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
W1012 08:45:44.922096    4771 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
W1012 08:45:54.956669    4771 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
W1012 08:46:04.987904    4771 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
W1012 08:46:15.052138    4771 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
W1012 08:46:25.096467    4771 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
W1012 08:46:35.130675    4771 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 ...
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-9b6w5				system-node-critical pod "calico-node-9b6w5" is pending
Pod	kube-system/calico-node-xskfv				system-node-critical pod "calico-node-xskfv" is pending
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jsqcj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jsqcj" is pending

Validation Failed
W1012 08:46:48.619275    4771 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/calico-node-9b6w5				system-node-critical pod "calico-node-9b6w5" is not ready (calico-node)
Pod	kube-system/calico-node-blp95				system-node-critical pod "calico-node-blp95" is pending
Pod	kube-system/calico-node-xskfv				system-node-critical pod "calico-node-xskfv" is pending
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-jsqcj		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-jsqcj" is pending

Validation Failed
W1012 08:47:01.055067    4771 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 13 lines ...
Pod	kube-system/calico-node-blp95				system-node-critical pod "calico-node-blp95" is not ready (calico-node)
Pod	kube-system/calico-node-qdh2j				system-node-critical pod "calico-node-qdh2j" is pending
Pod	kube-system/calico-node-xskfv				system-node-critical pod "calico-node-xskfv" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is pending

Validation Failed
W1012 08:47:13.548761    4771 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 9 lines ...
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-blp95				system-node-critical pod "calico-node-blp95" is not ready (calico-node)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:47:26.165402    4771 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 9 lines ...
KIND	NAME									MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6			system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs					system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl					system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-32-18.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-32-18.sa-east-1.compute.internal" is pending

Validation Failed
W1012 08:47:38.671276    4771 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 10 lines ...
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6			system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs					system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl					system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-50-145.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-50-145.sa-east-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-50-28.sa-east-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-50-28.sa-east-1.compute.internal" is pending

Validation Failed
W1012 08:47:51.106489    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:48:03.658322    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:48:16.135831    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:48:28.552228    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:48:40.999894    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:48:53.739667    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:49:06.177064    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:49:18.603565    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:49:31.200613    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:49:43.613071    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:49:56.069568    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:50:08.493425    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:50:20.894885    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:50:33.291605    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:50:46.212516    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:50:58.646489    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:51:11.251557    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:51:23.741785    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:51:36.291035    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:51:48.743482    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:52:01.109335    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:52:13.523079    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:52:25.987060    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:52:38.369129    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:52:50.787840    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:53:03.207176    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:53:15.785093    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:53:28.233896    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:53:40.630423    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:53:53.370345    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:54:05.763366    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:54:18.198825    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:54:30.696927    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:54:43.651839    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:54:56.103689    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:55:08.570544    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:55:21.071676    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:55:33.467121    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:55:45.935885    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:55:58.457119    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:56:10.887617    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:56:23.366442    4771 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-659bd7879c-hvxw6	system-cluster-critical pod "calico-kube-controllers-659bd7879c-hvxw6" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-64497985bd-2psrs			system-cluster-critical pod "coredns-64497985bd-2psrs" is not ready (coredns)
Pod	kube-system/coredns-64497985bd-kkcrl			system-cluster-critical pod "coredns-64497985bd-kkcrl" is not ready (coredns)

Validation Failed
W1012 08:56:35.887566    4771 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I1012 08:56:45.896881    4710 dumplogs.go:40] /logs/artifacts/ed6138e9-2b37-11ec-94fd-caf12f285ed9/kops toolbox dump --name e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1012 08:56:45.916372    4781 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1012 08:56:45.916507    4781 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/10/12 08:56:57 Dumping node ip-172-20-32-18.sa-east-1.compute.internal
2021/10/12 08:57:02 Dumping node ip-172-20-47-175.sa-east-1.compute.internal
2021/10/12 08:57:08 Dumping node ip-172-20-50-145.sa-east-1.compute.internal
... skipping 1231 lines ...
route-table:rtb-096a53874eb22cb44	ok
vpc:vpc-0e4b74055cd754996	ok
dhcp-options:dopt-0066d0f305417f6cf	ok
Deleted kubectl config for e2e-b6f30ae0f9-ec357.test-cncf-aws.k8s.io

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