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

No Test Failures!


Error lines from build-log.txt

... skipping 130 lines ...
I1011 07:43:00.086543    4731 up.go:43] Cleaning up any leaked resources from previous cluster
I1011 07:43:00.086577    4731 dumplogs.go:40] /logs/artifacts/a52585eb-2a66-11ec-b781-c649eef4635a/kops toolbox dump --name e2e-b7086869c4-da484.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1011 07:43:00.106036    4750 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1011 07:43:00.106152    4750 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-b7086869c4-da484.test-cncf-aws.k8s.io" not found
W1011 07:43:00.635199    4731 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1011 07:43:00.635262    4731 down.go:48] /logs/artifacts/a52585eb-2a66-11ec-b781-c649eef4635a/kops delete cluster --name e2e-b7086869c4-da484.test-cncf-aws.k8s.io --yes
I1011 07:43:00.650805    4761 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1011 07:43:00.650935    4761 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-b7086869c4-da484.test-cncf-aws.k8s.io" not found
I1011 07:43:01.196575    4731 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/11 07:43:01 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
I1011 07:43:01.203591    4731 http.go:37] curl https://ip.jsb.workers.dev
I1011 07:43:01.296957    4731 up.go:144] /logs/artifacts/a52585eb-2a66-11ec-b781-c649eef4635a/kops create cluster --name e2e-b7086869c4-da484.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20211001.1-x86_64-gp2 --channel=alpha --networking=cilium-etcd --container-runtime=containerd --admin-access 35.193.138.120/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ca-central-1a --master-size c5.large
I1011 07:43:01.312483    4771 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1011 07:43:01.312705    4771 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1011 07:43:01.370863    4771 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1011 07:43:01.885995    4771 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1011 07:43:25.747888    4731 up.go:181] /logs/artifacts/a52585eb-2a66-11ec-b781-c649eef4635a/kops validate cluster --name e2e-b7086869c4-da484.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1011 07:43:25.763969    4792 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1011 07:43:25.764239    4792 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-b7086869c4-da484.test-cncf-aws.k8s.io

W1011 07:43:26.808775    4792 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-b7086869c4-da484.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:43:36.850803    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:43:46.888480    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:43:56.934647    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:44:06.979753    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:44:17.027603    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:44:27.055313    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:44:37.085476    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:44:47.129832    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:44:57.158424    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:45:07.187792    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:45:17.216018    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:45:27.246102    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:45:37.288413    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:45:47.375250    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:45:57.415506    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:46:07.456019    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:46:17.483167    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:46:27.514724    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:46:37.547192    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:46:47.592642    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-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
W1011 07:46:57.627438    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:47:08.977310    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:47:19.946782    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:47:31.117105    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:47:42.022917    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:47:53.003095    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:48:03.860990    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:48:14.814733    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:48:25.759866    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:48:36.689254    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:48:47.592269    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:48:58.521523    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:49:09.425193    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:49:20.366663    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:49:31.226541    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:49:42.323579    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:49:53.288793    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:50:04.247450    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:50:15.137177    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:50:26.078628    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:50:36.969519    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:50:47.811744    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:50:58.811335    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:51:09.751408    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:51:20.630147    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:51:31.460897    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:51:42.335969    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:51:53.343065    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:52:04.271359    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:52:15.264761    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:52:26.152461    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:52:37.038855    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:52:47.898724    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:52:58.750784    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:53:09.609368    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:53:20.558864    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:53:31.496374    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:53:42.458434    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:53:53.310971    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:54:04.273582    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:54:15.116463    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:54:26.050514    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:54:36.948594    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:54:47.887660    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:54:58.856743    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:55:09.734567    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:55:20.732954    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:55:31.601528    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:55:42.531955    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:55:53.462387    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:56:04.376323    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:56:15.274990    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:56:26.256542    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:56:37.150525    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:56:48.095380    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:56:58.983513    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:57:09.871222    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:57:20.727647    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:57:31.673255    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:57:42.615808    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:57:53.634747    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:58:04.557956    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:58:15.582678    4792 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ca-central-1a	Master	c5.large	1	1	ca-central-1a
nodes-ca-central-1a	Node	t3.medium	4	4	ca-central-1a

... skipping 9 lines ...
Machine	i-0ed9234d614f9bd38				machine "i-0ed9234d614f9bd38" has not yet joined cluster
Node	ip-172-20-32-73.ca-central-1.compute.internal	node "ip-172-20-32-73.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-x7xgs			system-node-critical pod "cilium-x7xgs" is pending
Pod	kube-system/coredns-5dc785954d-pmwd8		system-cluster-critical pod "coredns-5dc785954d-pmwd8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-rss65	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-rss65" is pending

Validation Failed
W1011 07:58:26.491981    4792 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1011 07:58:36.499105    4731 dumplogs.go:40] /logs/artifacts/a52585eb-2a66-11ec-b781-c649eef4635a/kops toolbox dump --name e2e-b7086869c4-da484.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1011 07:58:36.518344    4802 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1011 07:58:36.518476    4802 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/11 07:58:42 Dumping node ip-172-20-32-73.ca-central-1.compute.internal
2021/10/11 07:58:44 dumping node not registered in kubernetes: 99.79.36.135
2021/10/11 07:58:44 Dumping node 99.79.36.135
... skipping 1237 lines ...
route-table:rtb-01282d9e957fb3e04	ok
vpc:vpc-05b6a7f1a65558cff	ok
dhcp-options:dopt-04f3bf916c9c485ee	ok
Deleted kubectl config for e2e-b7086869c4-da484.test-cncf-aws.k8s.io

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