This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-02 02:17
Elapsed17m52s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 124 lines ...
I0902 02:17:59.437821    4068 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.22/latest-ci-updown-green.txt
I0902 02:17:59.439551    4068 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.22.0-beta.2+v1.22.0-beta.1-12-gcdb33dd4c0/linux/amd64/kops
I0902 02:18:00.858613    4068 up.go:43] Cleaning up any leaked resources from previous cluster
I0902 02:18:00.858650    4068 dumplogs.go:38] /logs/artifacts/d00cf4ed-0b93-11ec-af6c-e6bbdd2c6991/kops toolbox dump --name e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0902 02:18:00.883537    4089 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0902 02:18:00.883701    4089 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io" not found
W0902 02:18:01.365470    4068 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0902 02:18:01.365539    4068 down.go:48] /logs/artifacts/d00cf4ed-0b93-11ec-af6c-e6bbdd2c6991/kops delete cluster --name e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io --yes
I0902 02:18:01.382836    4099 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0902 02:18:01.382947    4099 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io" not found
I0902 02:18:01.865662    4068 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/02 02:18:01 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404
I0902 02:18:01.874026    4068 http.go:37] curl https://ip.jsb.workers.dev
I0902 02:18:01.972141    4068 up.go:144] /logs/artifacts/d00cf4ed-0b93-11ec-af6c-e6bbdd2c6991/kops create cluster --name e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.4 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.3_HVM-20210209-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 34.69.66.225/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I0902 02:18:01.990492    4109 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0902 02:18:01.990652    4109 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0902 02:18:02.018277    4109 create_cluster.go:827] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0902 02:18:02.536002    4109 new_cluster.go:1055]  Cloud Provider ID = aws
... skipping 46 lines ...

I0902 02:18:27.098847    4068 up.go:181] /logs/artifacts/d00cf4ed-0b93-11ec-af6c-e6bbdd2c6991/kops validate cluster --name e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0902 02:18:27.118550    4129 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0902 02:18:27.118832    4129 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io

W0902 02:18:28.165029    4129 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-d6bb2d448e-7012d.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
W0902 02:18:38.197488    4129 validate_cluster.go:232] (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
W0902 02:18:48.234299    4129 validate_cluster.go:232] (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
W0902 02:18:58.279928    4129 validate_cluster.go:232] (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
W0902 02:19:08.309434    4129 validate_cluster.go:232] (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
W0902 02:19:18.341773    4129 validate_cluster.go:232] (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
W0902 02:19:28.390366    4129 validate_cluster.go:232] (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
W0902 02:19:38.424283    4129 validate_cluster.go:232] (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
W0902 02:19:48.472272    4129 validate_cluster.go:232] (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
W0902 02:19:58.509534    4129 validate_cluster.go:232] (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
W0902 02:20:08.541172    4129 validate_cluster.go:232] (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
W0902 02:20:18.588304    4129 validate_cluster.go:232] (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
W0902 02:20:28.617656    4129 validate_cluster.go:232] (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
W0902 02:20:38.645884    4129 validate_cluster.go:232] (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
W0902 02:20:48.681612    4129 validate_cluster.go:232] (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
W0902 02:20:58.714191    4129 validate_cluster.go:232] (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
W0902 02:21:08.760618    4129 validate_cluster.go:232] (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
W0902 02:21:18.794160    4129 validate_cluster.go:232] (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
W0902 02:21:28.837479    4129 validate_cluster.go:232] (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
W0902 02:21:38.983322    4129 validate_cluster.go:232] (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
W0902 02:21:49.028476    4129 validate_cluster.go:232] (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
W0902 02:21:59.076799    4129 validate_cluster.go:232] (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
W0902 02:22:09.109614    4129 validate_cluster.go:232] (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
W0902 02:22:19.147093    4129 validate_cluster.go:232] (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
W0902 02:22:29.181510    4129 validate_cluster.go:232] (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
W0902 02:22:39.215950    4129 validate_cluster.go:232] (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
W0902 02:22:49.291933    4129 validate_cluster.go:232] (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
W0902 02:22:59.321079    4129 validate_cluster.go:232] (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
W0902 02:23:09.367322    4129 validate_cluster.go:232] (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
W0902 02:23:19.396601    4129 validate_cluster.go:232] (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
W0902 02:23:29.430788    4129 validate_cluster.go:232] (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
W0902 02:23:39.466041    4129 validate_cluster.go:232] (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
W0902 02:23:49.496477    4129 validate_cluster.go:232] (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
W0902 02:23:59.531958    4129 validate_cluster.go:232] (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
W0902 02:24:09.579385    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:24:21.548493    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:24:33.558615    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:24:44.878857    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:24:56.383221    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:25:07.711024    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:25:19.020066    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:25:30.516852    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:25:41.875344    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:25:53.254459    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:26:05.691629    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:26:17.109404    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:26:28.491790    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:26:39.933299    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:26:51.235391    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:27:02.786950    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:27:14.175959    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:27:25.565073    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:27:37.034173    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:27:48.414591    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:27:59.817203    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:28:11.330017    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:28:22.686502    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:28:34.087681    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:28:45.474654    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:28:56.967135    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:29:08.272179    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:29:19.584960    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:29:31.015634    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:29:42.459950    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:29:53.752254    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:30:05.156061    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:30:16.590107    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:30:27.972142    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:30:39.367377    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:30:50.653344    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:31:02.600638    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:31:14.011517    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:31:25.441252    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:31:36.909480    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:31:48.467085    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:31:59.974579    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:32:12.429739    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:32:23.845702    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:32:35.256062    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:32:46.870960    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:32:58.357326    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:33:09.745860    4129 validate_cluster.go:232] (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-0a0999647e71ca7ea				machine "i-0a0999647e71ca7ea" has not yet joined cluster
Node	ip-172-20-49-217.us-west-2.compute.internal	node "ip-172-20-49-217.us-west-2.compute.internal" of role "master" is not ready
Pod	kube-system/cilium-hrjmh			system-node-critical pod "cilium-hrjmh" is pending
Pod	kube-system/coredns-5dc785954d-5hvq7		system-cluster-critical pod "coredns-5dc785954d-5hvq7" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-78dnj	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-78dnj" is pending

Validation Failed
W0902 02:33:21.187326    4129 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0902 02:33:31.198479    4068 dumplogs.go:38] /logs/artifacts/d00cf4ed-0b93-11ec-af6c-e6bbdd2c6991/kops toolbox dump --name e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I0902 02:33:31.222849    4140 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0902 02:33:31.222957    4140 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/02 02:33:39 Dumping node ip-172-20-49-217.us-west-2.compute.internal
2021/09/02 02:33:42 dumping node not registered in kubernetes: 34.221.109.66
2021/09/02 02:33:42 Dumping node 34.221.109.66
... skipping 1192 lines ...
route-table:rtb-066f3536bc3be9297	ok
vpc:vpc-08841b9e94efa5108	ok
dhcp-options:dopt-035f069bddf0be23e	ok
Deleted kubectl config for e2e-d6bb2d448e-7012d.test-cncf-aws.k8s.io

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