This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-12 01:08
Elapsed19m41s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 130 lines ...
I1012 01:09:05.159820    4748 up.go:43] Cleaning up any leaked resources from previous cluster
I1012 01:09:05.159996    4748 dumplogs.go:40] /logs/artifacts/c86afc95-2af8-11ec-94fd-caf12f285ed9/kops toolbox dump --name e2e-cf1c54603b-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1012 01:09:05.194459    4768 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1012 01:09:05.194843    4768 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-cf1c54603b-99215.test-cncf-aws.k8s.io" not found
W1012 01:09:05.860240    4748 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1012 01:09:05.860300    4748 down.go:48] /logs/artifacts/c86afc95-2af8-11ec-94fd-caf12f285ed9/kops delete cluster --name e2e-cf1c54603b-99215.test-cncf-aws.k8s.io --yes
I1012 01:09:05.891352    4779 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1012 01:09:05.891592    4779 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-cf1c54603b-99215.test-cncf-aws.k8s.io" not found
I1012 01:09:06.564664    4748 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/12 01:09:06 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
I1012 01:09:06.574540    4748 http.go:37] curl https://ip.jsb.workers.dev
I1012 01:09:06.678762    4748 up.go:144] /logs/artifacts/c86afc95-2af8-11ec-94fd-caf12f285ed9/kops create cluster --name e2e-cf1c54603b-99215.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=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 35.239.83.195/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-west-2a --master-size c5.large
I1012 01:09:06.715948    4790 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1012 01:09:06.716105    4790 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1012 01:09:06.838642    4790 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1012 01:09:07.433533    4790 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I1012 01:09:33.623118    4748 up.go:181] /logs/artifacts/c86afc95-2af8-11ec-94fd-caf12f285ed9/kops validate cluster --name e2e-cf1c54603b-99215.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1012 01:09:33.659985    4811 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1012 01:09:33.660257    4811 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-cf1c54603b-99215.test-cncf-aws.k8s.io

W1012 01:09:34.929523    4811 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-cf1c54603b-99215.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
W1012 01:09:44.975531    4811 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
W1012 01:09:55.021211    4811 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
W1012 01:10:05.054706    4811 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
W1012 01:10:15.088041    4811 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
W1012 01:10:25.118448    4811 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
W1012 01:10:35.161779    4811 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
W1012 01:10:45.194003    4811 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
W1012 01:10:55.232044    4811 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
W1012 01:11:05.262475    4811 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
W1012 01:11:15.292866    4811 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
W1012 01:11:25.327903    4811 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
W1012 01:11:35.377560    4811 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
W1012 01:11:45.425870    4811 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
W1012 01:11:55.457454    4811 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
W1012 01:12:05.489837    4811 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
W1012 01:12:15.555907    4811 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
W1012 01:12:25.585206    4811 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
W1012 01:12:35.617301    4811 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
W1012 01:12:45.648583    4811 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
W1012 01:12:55.679615    4811 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
W1012 01:13:05.718211    4811 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
W1012 01:13:15.766015    4811 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
W1012 01:13:25.812046    4811 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
W1012 01:13:35.846028    4811 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
W1012 01:13:45.890196    4811 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
W1012 01:13:55.930328    4811 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
W1012 01:14:05.978766    4811 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
W1012 01:14:16.010996    4811 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
W1012 01:14:26.039991    4811 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
W1012 01:14:36.085508    4811 validate_cluster.go:221] (will retry): cluster not yet healthy
W1012 01:15:16.125576    4811 validate_cluster.go:173] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-cf1c54603b-99215.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-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
... skipping 8 lines ...
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-d4vrw				system-node-critical pod "calico-node-d4vrw" is not ready (calico-node)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:15:28.492635    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:15:40.116342    4811 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 ...
KIND	NAME									MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m			system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g					system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8					system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-54-236.us-west-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-54-236.us-west-2.compute.internal" is pending

Validation Failed
W1012 01:15:51.592105    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:16:03.103749    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:16:14.537251    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:16:26.044306    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:16:38.499518    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:16:49.919905    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:17:01.326917    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:17:12.733717    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:17:24.129140    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:17:35.597404    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:17:47.171534    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:17:58.567670    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:18:09.975764    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:18:21.502712    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:18:32.911393    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:18:44.400537    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:18:55.904918    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:19:07.289598    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:19:19.094942    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:19:30.645032    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:19:42.038267    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:19:53.415553    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:20:04.773771    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:20:16.157384    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:20:27.714940    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:20:39.095366    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:20:50.442836    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:21:01.934366    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:21:13.383604    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:21:24.787892    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:21:36.286501    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:21:47.727654    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:21:59.207457    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:22:10.660301    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:22:22.099832    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:22:33.621347    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:22:45.096214    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:22:56.484239    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:23:07.926376    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:23:19.621281    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:23:31.074312    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:23:42.637317    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:23:54.115532    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:24:05.545789    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:24:17.211329    4811 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 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-zcl5m	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-zcl5m" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-nsq4g			system-cluster-critical pod "coredns-5dc785954d-nsq4g" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-vwns8			system-cluster-critical pod "coredns-5dc785954d-vwns8" is not ready (coredns)

Validation Failed
W1012 01:24:28.668831    4811 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1012 01:24:38.677578    4748 dumplogs.go:40] /logs/artifacts/c86afc95-2af8-11ec-94fd-caf12f285ed9/kops toolbox dump --name e2e-cf1c54603b-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1012 01:24:38.697772    4821 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1012 01:24:38.697947    4821 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/12 01:24:47 Dumping node ip-172-20-36-100.us-west-2.compute.internal
2021/10/12 01:24:50 Dumping node ip-172-20-50-222.us-west-2.compute.internal
2021/10/12 01:24:52 Dumping node ip-172-20-50-40.us-west-2.compute.internal
... skipping 1401 lines ...
route-table:rtb-0b3b323e37d4e25bf	ok
vpc:vpc-05d0d8d1ef7b1e6bd	ok
dhcp-options:dopt-02f92fe4391dcd788	ok
Deleted kubectl config for e2e-cf1c54603b-99215.test-cncf-aws.k8s.io

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