This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-16 20:03
Elapsed18m2s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 131 lines ...
I1016 20:03:54.223754    4708 up.go:43] Cleaning up any leaked resources from previous cluster
I1016 20:03:54.223789    4708 dumplogs.go:40] /logs/artifacts/03533d88-2ebc-11ec-8a05-6acfde499713/kops toolbox dump --name e2e-136707abc8-e7a62.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1016 20:03:54.238923    4726 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1016 20:03:54.239025    4726 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-136707abc8-e7a62.test-cncf-aws.k8s.io" not found
W1016 20:03:54.760993    4708 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1016 20:03:54.761035    4708 down.go:48] /logs/artifacts/03533d88-2ebc-11ec-8a05-6acfde499713/kops delete cluster --name e2e-136707abc8-e7a62.test-cncf-aws.k8s.io --yes
I1016 20:03:54.776691    4738 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1016 20:03:54.776862    4738 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-136707abc8-e7a62.test-cncf-aws.k8s.io" not found
I1016 20:03:55.301555    4708 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/16 20:03:55 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
I1016 20:03:55.308930    4708 http.go:37] curl https://ip.jsb.workers.dev
I1016 20:03:55.399667    4708 up.go:144] /logs/artifacts/03533d88-2ebc-11ec-8a05-6acfde499713/kops create cluster --name e2e-136707abc8-e7a62.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.20.11 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=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.194.23.235/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ca-central-1a --master-size c5.large
I1016 20:03:55.413881    4748 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1016 20:03:55.413952    4748 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1016 20:03:55.455022    4748 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1016 20:03:56.054746    4748 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1016 20:04:18.750548    4708 up.go:181] /logs/artifacts/03533d88-2ebc-11ec-8a05-6acfde499713/kops validate cluster --name e2e-136707abc8-e7a62.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1016 20:04:18.766037    4769 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1016 20:04:18.766689    4769 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-136707abc8-e7a62.test-cncf-aws.k8s.io

W1016 20:04:19.736749    4769 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-136707abc8-e7a62.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1016 20:04:29.772110    4769 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-136707abc8-e7a62.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
W1016 20:04:39.802768    4769 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
W1016 20:04:49.838029    4769 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
W1016 20:04:59.887640    4769 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
W1016 20:05:09.951765    4769 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
W1016 20:05:19.989351    4769 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
W1016 20:05:30.017831    4769 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
W1016 20:05:40.063581    4769 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
W1016 20:05:50.105953    4769 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
W1016 20:06:00.166408    4769 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
W1016 20:06:10.209324    4769 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
W1016 20:06:20.259248    4769 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 20:06:30.279272    4769 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-136707abc8-e7a62.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
W1016 20:06:40.338559    4769 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 20:06:50.367524    4769 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-136707abc8-e7a62.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
W1016 20:07:00.414117    4769 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
W1016 20:07:10.444413    4769 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
W1016 20:07:20.477756    4769 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
W1016 20:07:30.509292    4769 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
W1016 20:07:40.541237    4769 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
W1016 20:07:50.604761    4769 validate_cluster.go:221] (will retry): cluster not yet healthy
W1016 20:08:00.621445    4769 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-136707abc8-e7a62.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
... skipping 8 lines ...
Machine	i-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:08:11.916908    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:08:22.876198    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:08:33.860243    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:08:44.751031    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:08:55.703058    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:09:06.692363    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:09:17.671856    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:09:28.591646    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:09:39.581356    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:09:50.495641    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:10:01.467549    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:10:12.480588    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:10:23.449216    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:10:34.451835    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:10:45.410078    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:10:56.402368    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:11:07.340275    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:11:18.374649    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:11:29.282482    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:11:40.292715    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:11:51.214896    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:12:02.332013    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:12:13.311888    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:12:24.268147    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:12:35.166188    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:12:46.209240    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:12:57.101230    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:13:08.059442    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:13:18.961931    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:13:29.920113    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:13:40.977522    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:13:51.830580    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:14:02.787908    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:14:13.683212    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:14:24.608994    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:14:35.512771    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:14:46.394687    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:14:57.411395    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:15:08.333985    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:15:19.264039    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:15:30.193930    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:15:41.030200    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:15:51.994734    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:16:03.067988    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:16:14.071122    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:16:25.030413    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:16:35.976558    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:16:46.901382    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:16:57.863252    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:17:08.776903    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:17:19.710352    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:17:30.602654    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:17:41.556427    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:17:52.489009    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:18:03.393371    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:18:14.308715    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:18:25.188323    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:18:36.181321    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:18:47.133172    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:18:58.017376    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:19:09.002534    4769 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-0d0d2d7e8ed17ae64				machine "i-0d0d2d7e8ed17ae64" has not yet joined cluster
Node	ip-172-20-47-174.ca-central-1.compute.internal	node "ip-172-20-47-174.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-bh9d7			system-node-critical pod "cilium-bh9d7" is pending
Pod	kube-system/coredns-64497985bd-ntj7c		system-cluster-critical pod "coredns-64497985bd-ntj7c" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-f57xj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-f57xj" is pending

Validation Failed
W1016 20:19:19.914257    4769 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1016 20:19:29.918820    4708 dumplogs.go:40] /logs/artifacts/03533d88-2ebc-11ec-8a05-6acfde499713/kops toolbox dump --name e2e-136707abc8-e7a62.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1016 20:19:29.933843    4780 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1016 20:19:29.933927    4780 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/16 20:19:35 Dumping node ip-172-20-47-174.ca-central-1.compute.internal
2021/10/16 20:19:37 dumping node not registered in kubernetes: 99.79.54.214
2021/10/16 20:19:37 Dumping node 99.79.54.214
... skipping 1223 lines ...
route-table:rtb-01ea84b7579f0f3a7	ok
vpc:vpc-0bb93157617f4d257	ok
dhcp-options:dopt-0c6d078b69c9cf81e	ok
Deleted kubectl config for e2e-136707abc8-e7a62.test-cncf-aws.k8s.io

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