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

No Test Failures!


Error lines from build-log.txt

... skipping 134 lines ...
I1004 07:42:34.849929    4710 up.go:43] Cleaning up any leaked resources from previous cluster
I1004 07:42:34.849970    4710 dumplogs.go:40] /logs/artifacts/6b6afa90-24e6-11ec-b766-fab168edef1d/kops toolbox dump --name e2e-129af6f5a1-da484.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1004 07:42:34.869117    4731 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1004 07:42:34.869247    4731 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-129af6f5a1-da484.test-cncf-aws.k8s.io" not found
W1004 07:42:35.405999    4710 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1004 07:42:35.406081    4710 down.go:48] /logs/artifacts/6b6afa90-24e6-11ec-b766-fab168edef1d/kops delete cluster --name e2e-129af6f5a1-da484.test-cncf-aws.k8s.io --yes
I1004 07:42:35.426536    4741 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1004 07:42:35.426667    4741 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-129af6f5a1-da484.test-cncf-aws.k8s.io" not found
I1004 07:42:35.922015    4710 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/04 07:42:35 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
I1004 07:42:35.930639    4710 http.go:37] curl https://ip.jsb.workers.dev
I1004 07:42:36.016197    4710 up.go:144] /logs/artifacts/6b6afa90-24e6-11ec-b766-fab168edef1d/kops create cluster --name e2e-129af6f5a1-da484.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=amazon/amzn2-ami-kernel-5.10-hvm-2.0.20210813.1-x86_64-gp2 --channel=alpha --networking=cilium-etcd --container-runtime=containerd --admin-access 35.222.83.205/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I1004 07:42:36.034648    4751 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1004 07:42:36.034795    4751 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1004 07:42:36.086391    4751 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1004 07:42:36.685700    4751 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1004 07:43:02.652323    4710 up.go:181] /logs/artifacts/6b6afa90-24e6-11ec-b766-fab168edef1d/kops validate cluster --name e2e-129af6f5a1-da484.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1004 07:43:02.674531    4771 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1004 07:43:02.674654    4771 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-129af6f5a1-da484.test-cncf-aws.k8s.io

W1004 07:43:03.844096    4771 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-129af6f5a1-da484.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:43:13.877356    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:43:23.909756    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:43:33.948113    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:43:43.993590    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:43:54.022256    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:44:04.052439    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:44:14.087372    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:44:24.149819    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
W1004 07:44:34.169504    4771 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-129af6f5a1-da484.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:44:44.201786    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:44:54.244438    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:45:04.277100    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:45:14.321898    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:45:24.363546    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:45:34.391965    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:45:44.422663    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:45:54.455080    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:46:04.483515    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:46:14.518636    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:46:24.548624    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:46:34.611653    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:46:44.641756    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:46:54.672228    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:47:04.722168    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

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
W1004 07:47:14.751131    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:47:26.743134    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:47:38.232324    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:47:49.773024    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:48:01.268173    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:48:12.731636    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:48:24.078005    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:48:35.499686    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:48:46.844795    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:48:58.228281    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:49:09.671277    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:49:21.079217    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:49:32.476981    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:49:43.856616    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:49:55.244022    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:50:06.700649    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:50:18.073231    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:50:29.465350    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:50:40.868126    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:50:52.298914    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:51:03.710748    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:51:15.102508    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:51:26.741990    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:51:38.164833    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:51:49.765611    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:52:01.211525    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:52:12.610801    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:52:24.224132    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:52:35.636484    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:52:47.147177    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:52:58.639664    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:53:10.137923    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:53:21.545607    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:53:32.914848    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:53:44.357348    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:53:56.276940    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:54:07.745967    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:54:19.165589    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:54:30.614599    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:54:41.969405    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:54:53.471601    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:55:04.930507    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:55:16.644120    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:55:27.982790    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:55:40.241922    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:55:51.624039    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:56:03.150676    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:56:14.512041    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:56:25.929103    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:56:37.355248    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:56:48.713805    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:57:00.126208    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:57:11.418010    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:57:22.868493    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:57:34.325125    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:57:45.771912    4771 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-west-2a	Master	c5.large	1	1	us-west-2a
nodes-us-west-2a	Node	t3.medium	4	4	us-west-2a

... skipping 9 lines ...
Machine	i-0745420c9a0a035c4				machine "i-0745420c9a0a035c4" has not yet joined cluster
Node	ip-172-20-60-94.us-west-2.compute.internal	node "ip-172-20-60-94.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-77bb8			system-node-critical pod "cilium-77bb8" is pending
Pod	kube-system/coredns-5dc785954d-rslcg		system-cluster-critical pod "coredns-5dc785954d-rslcg" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-st2ss	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-st2ss" is pending

Validation Failed
W1004 07:57:57.266677    4771 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1004 07:58:07.275963    4710 dumplogs.go:40] /logs/artifacts/6b6afa90-24e6-11ec-b766-fab168edef1d/kops toolbox dump --name e2e-129af6f5a1-da484.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1004 07:58:07.294828    4782 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1004 07:58:07.294954    4782 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/04 07:58:15 Dumping node ip-172-20-60-94.us-west-2.compute.internal
2021/10/04 07:58:19 dumping node not registered in kubernetes: 34.221.108.226
2021/10/04 07:58:19 Dumping node 34.221.108.226
... skipping 1259 lines ...
route-table:rtb-05bd8f4ef47aa9eb7	ok
vpc:vpc-095d81f0e940dde3d	ok
dhcp-options:dopt-017815fd434551e61	ok
Deleted kubectl config for e2e-129af6f5a1-da484.test-cncf-aws.k8s.io

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