This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2023-01-10 17:08
Elapsed20m28s
Revisionmaster

Test Failures


kubetest2 Up 16m0s

exit status 1
				from junit_runner.xml

Filter through log files


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 136 lines ...
I0110 17:10:10.727235    5486 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.26.0-beta.2+v1.26.0-beta.1-40-gf1bad9a1e3/linux/amd64/kops
I0110 17:10:11.550646    5486 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519
I0110 17:10:11.564468    5486 up.go:44] Cleaning up any leaked resources from previous cluster
I0110 17:10:11.564740    5486 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0110 17:10:11.564885    5486 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0110 17:10:11.607313    5509 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io" not found
W0110 17:10:12.087694    5486 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0110 17:10:12.087749    5486 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --yes
I0110 17:10:12.087763    5486 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --yes
I0110 17:10:12.133901    5520 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io" not found
I0110 17:10:12.603251    5486 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2023/01/10 17:10:12 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
I0110 17:10:12.621143    5486 http.go:37] curl https://ip.jsb.workers.dev
I0110 17:10:12.766546    5486 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.7.0_HVM-20221101-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-eni --container-runtime=docker --admin-access 34.67.147.98/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0110 17:10:12.766581    5486 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.7.0_HVM-20221101-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-eni --container-runtime=docker --admin-access 34.67.147.98/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones sa-east-1a --master-size c5.large
I0110 17:10:12.806643    5530 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0110 17:10:12.823942    5530 create_cluster.go:878] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0110 17:10:13.333519    5530 new_cluster.go:1338] Cloud Provider ID: "aws"
... skipping 535 lines ...

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 control plane node 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
W0110 17:11:01.771429    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:11:11.822417    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:11:21.862856    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:11:31.907361    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:11:41.953155    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:11:51.989510    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:12:02.028036    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:12:12.073839    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:12:22.115573    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:12:32.153643    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:12:42.203306    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:12:52.243525    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:13:02.298112    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:13:12.338593    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:13:22.372602    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:13:32.415706    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:13:42.452265    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:13:52.504292    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:14:02.542542    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:14:12.581757    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:14:22.625288    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:14:32.846040    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:14:42.883438    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:14:52.921556    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:15:02.964351    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:15:13.003462    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:15:23.040640    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:15:33.082813    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:15:43.124320    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:15:53.176401    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:16:03.226415    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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 control plane node 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
W0110 17:16:13.266403    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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/cilium-8nb5q			system-node-critical pod "cilium-8nb5q" is not ready (cilium-agent)
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending
Pod	kube-system/ebs-csi-controller-6b8447c4f-nnlqz	system-cluster-critical pod "ebs-csi-controller-6b8447c4f-nnlqz" is pending
Pod	kube-system/ebs-csi-node-pd9ll			system-node-critical pod "ebs-csi-node-pd9ll" is pending

Validation Failed
W0110 17:16:27.001380    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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/cilium-8nb5q			system-node-critical pod "cilium-8nb5q" is not ready (cilium-agent)
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending
Pod	kube-system/ebs-csi-controller-6b8447c4f-nnlqz	system-cluster-critical pod "ebs-csi-controller-6b8447c4f-nnlqz" is pending
Pod	kube-system/ebs-csi-node-pd9ll			system-node-critical pod "ebs-csi-node-pd9ll" is pending

Validation Failed
W0110 17:16:39.572003    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	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/cilium-8nb5q			system-node-critical pod "cilium-8nb5q" is not ready (cilium-agent)
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending
Pod	kube-system/ebs-csi-controller-6b8447c4f-nnlqz	system-cluster-critical pod "ebs-csi-controller-6b8447c4f-nnlqz" is pending
Pod	kube-system/ebs-csi-node-pd9ll			system-node-critical pod "ebs-csi-node-pd9ll" is pending

Validation Failed
W0110 17:16:52.113868    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending
Pod	kube-system/ebs-csi-controller-6b8447c4f-nnlqz	system-cluster-critical pod "ebs-csi-controller-6b8447c4f-nnlqz" is pending
Pod	kube-system/ebs-csi-node-pd9ll			system-node-critical pod "ebs-csi-node-pd9ll" is pending

Validation Failed
W0110 17:17:04.713775    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 9 lines ...
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending
Pod	kube-system/ebs-csi-controller-6b8447c4f-nnlqz	system-cluster-critical pod "ebs-csi-controller-6b8447c4f-nnlqz" is pending
Pod	kube-system/ebs-csi-node-pd9ll			system-node-critical pod "ebs-csi-node-pd9ll" is pending

Validation Failed
W0110 17:17:17.218906    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:17:29.803899    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:17:42.264933    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:17:54.698883    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:18:07.127737    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:18:19.559624    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:18:31.997501    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:18:44.414539    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:18:56.800478    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:19:09.316092    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:19:21.742069    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:19:34.155110    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:19:46.620485    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:19:59.117353    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:20:11.585403    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:20:24.554662    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:20:37.177197    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:20:49.626106    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:21:02.112348    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:21:14.585186    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:21:27.014620    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:21:39.419614    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:21:52.095593    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:22:04.582917    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:22:17.069364    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:22:29.498212    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:22:41.902669    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:22:54.377298    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:23:06.859414    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:23:19.307963    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:23:31.710724    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:23:44.120315    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:23:56.623709    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:24:09.028710    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:24:22.131344    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:24:34.573455    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:24:47.053050    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:24:59.475110    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:25:11.815597    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:25:24.179899    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:25:36.567516    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:25:49.005662    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME				ROLE		MACHINETYPE	MIN	MAX	SUBNETS
control-plane-sa-east-1a	ControlPlane	c5.large	1	1	sa-east-1a
nodes-sa-east-1a		Node		t3.medium	4	4	sa-east-1a

... skipping 7 lines ...
Machine	i-060913ea2614a29ee				machine "i-060913ea2614a29ee" has not yet joined cluster
Machine	i-07c704708443ed6bf				machine "i-07c704708443ed6bf" has not yet joined cluster
Machine	i-0855710f6846aabc5				machine "i-0855710f6846aabc5" has not yet joined cluster
Pod	kube-system/coredns-867df8f45c-d6vgt		system-cluster-critical pod "coredns-867df8f45c-d6vgt" is pending
Pod	kube-system/coredns-autoscaler-557ccb4c66-tqtdc	system-cluster-critical pod "coredns-autoscaler-557ccb4c66-tqtdc" is pending

Validation Failed
W0110 17:26:01.458149    5567 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: validation failed: wait time exceeded during validation
I0110 17:26:11.465794    5486 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0110 17:26:11.465961    5486 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/557142ab-9109-11ed-91e1-de8b26bb5f42/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0110 17:26:11.513016    5578 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
W0110 17:26:21.985678    5578 aws.go:2059] could not find instance profile "nodes.e2e-e2e-kops-aws-updown.test-cncf-aws.k8s.io". Resource may already have been deleted: NoSuchEntity: Instance Profile nodes.e2e-e2e-kops-aws-updown.test-cncf-aws.k8s.io cannot be found.
	status code: 404, request id: a521380a-971e-4365-b577-ecc4dcf20e48
2023/01/10 17:26:32 Dumping node ip-172-20-32-133.sa-east-1.compute.internal
... skipping 268 lines ...
route-table:rtb-0979fec2d96548bd9	ok
vpc:vpc-01f4a8cde146b5d17	ok
dhcp-options:dopt-04987bb5db82348a6	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace