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

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1002 20:04:29.204144    4732 up.go:43] Cleaning up any leaked resources from previous cluster
I1002 20:04:29.204181    4732 dumplogs.go:40] /logs/artifacts/bdb93876-23bb-11ec-b766-fab168edef1d/kops toolbox dump --name e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1002 20:04:29.221713    4751 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1002 20:04:29.222415    4751 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io" not found
W1002 20:04:29.758299    4732 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1002 20:04:29.758348    4732 down.go:48] /logs/artifacts/bdb93876-23bb-11ec-b766-fab168edef1d/kops delete cluster --name e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io --yes
I1002 20:04:29.777928    4762 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1002 20:04:29.778941    4762 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io" not found
I1002 20:04:30.322258    4732 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/02 20:04:30 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
I1002 20:04:30.330326    4732 http.go:37] curl https://ip.jsb.workers.dev
I1002 20:04:30.420265    4732 up.go:144] /logs/artifacts/bdb93876-23bb-11ec-b766-fab168edef1d/kops create cluster --name e2e-a431abb7d3-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.20210813.1-x86_64-gp2 --channel=alpha --networking=cilium-etcd --container-runtime=containerd --admin-access 34.123.251.80/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ca-central-1a --master-size c5.large
I1002 20:04:30.438587    4772 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1002 20:04:30.438700    4772 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1002 20:04:30.485211    4772 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1002 20:04:31.143085    4772 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1002 20:04:57.025380    4732 up.go:181] /logs/artifacts/bdb93876-23bb-11ec-b766-fab168edef1d/kops validate cluster --name e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1002 20:04:57.044537    4793 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1002 20:04:57.044685    4793 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io

W1002 20:04:58.083372    4793 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a431abb7d3-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
W1002 20:05:08.117486    4793 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
W1002 20:05:18.153354    4793 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
W1002 20:05:28.182127    4793 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
W1002 20:05:38.213094    4793 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
W1002 20:05:48.243464    4793 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
W1002 20:05:58.274261    4793 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
W1002 20:06:08.303736    4793 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
W1002 20:06:18.336044    4793 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
W1002 20:06:28.373027    4793 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
W1002 20:06:38.405100    4793 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
W1002 20:06:48.454127    4793 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
W1002 20:06:58.492997    4793 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
W1002 20:07:08.540689    4793 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
W1002 20:07:18.574723    4793 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
W1002 20:07:28.605918    4793 validate_cluster.go:221] (will retry): cluster not yet healthy
W1002 20:07:38.623528    4793 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-a431abb7d3-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
W1002 20:07:48.652086    4793 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
W1002 20:07:58.695235    4793 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
W1002 20:08:08.742912    4793 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
W1002 20:08:18.774676    4793 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
W1002 20:08:28.810367    4793 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
W1002 20:08:38.845957    4793 validate_cluster.go:221] (will retry): cluster not yet healthy
W1002 20:09:18.881727    4793 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:09:30.112420    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:09:41.071964    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:09:52.055135    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:10:03.075502    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:10:14.073231    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:10:24.973240    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:10:35.847405    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:10:46.840094    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:10:57.812208    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:11:08.627477    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:11:19.537783    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:11:30.612906    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:11:41.605009    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:11:52.688225    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:12:03.621635    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:12:14.653655    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:12:25.649777    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:12:36.493388    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:12:47.474345    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:12:58.438549    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:13:09.386865    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:13:20.416761    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:13:31.396758    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:13:42.260510    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:13:53.144982    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:14:04.045869    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:14:14.963506    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:14:25.918466    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:14:36.880689    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:14:47.729527    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:14:58.798417    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:15:09.713218    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:15:20.599769    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:15:31.530759    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:15:42.432223    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:15:53.415129    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:16:04.325132    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:16:15.204999    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:16:26.058054    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:16:36.952384    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:16:47.847974    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:16:58.677611    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:17:09.641597    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:17:20.670454    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:17:31.558726    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:17:42.459984    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:17:53.379749    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:18:04.237465    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:18:15.175566    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:18:26.057673    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:18:36.907340    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:18:47.782496    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:18:58.712629    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:19:09.682154    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:19:20.635709    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:19:31.613513    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:19:42.586463    4793 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-0b4a510d4c1871add				machine "i-0b4a510d4c1871add" has not yet joined cluster
Node	ip-172-20-48-17.ca-central-1.compute.internal	node "ip-172-20-48-17.ca-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-7lw6x			system-node-critical pod "cilium-7lw6x" is pending
Pod	kube-system/coredns-64497985bd-qgdp8		system-cluster-critical pod "coredns-64497985bd-qgdp8" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-pxh6v	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-pxh6v" is pending

Validation Failed
W1002 20:19:53.531553    4793 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1002 20:20:03.541125    4732 dumplogs.go:40] /logs/artifacts/bdb93876-23bb-11ec-b766-fab168edef1d/kops toolbox dump --name e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1002 20:20:03.561296    4807 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1002 20:20:03.561432    4807 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/02 20:20:11 Dumping node ip-172-20-48-17.ca-central-1.compute.internal
2021/10/02 20:20:13 dumping node not registered in kubernetes: 3.96.216.37
2021/10/02 20:20:13 Dumping node 3.96.216.37
... skipping 1229 lines ...
route-table:rtb-035621dadaab0f161	ok
vpc:vpc-0dc4b6b95621a030f	ok
dhcp-options:dopt-07fe2409b4846feaa	ok
Deleted kubectl config for e2e-a431abb7d3-e7a62.test-cncf-aws.k8s.io

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