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

No Test Failures!


Error lines from build-log.txt

... skipping 130 lines ...
I1010 09:24:47.452476    4686 up.go:43] Cleaning up any leaked resources from previous cluster
I1010 09:24:47.452689    4686 dumplogs.go:40] /logs/artifacts/ba083a13-29ab-11ec-b781-c649eef4635a/kops toolbox dump --name e2e-820e751628-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1010 09:24:47.474142    4706 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1010 09:24:47.474408    4706 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-820e751628-53349.test-cncf-aws.k8s.io" not found
W1010 09:24:47.964116    4686 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1010 09:24:47.964152    4686 down.go:48] /logs/artifacts/ba083a13-29ab-11ec-b781-c649eef4635a/kops delete cluster --name e2e-820e751628-53349.test-cncf-aws.k8s.io --yes
I1010 09:24:47.977892    4715 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1010 09:24:47.977962    4715 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-820e751628-53349.test-cncf-aws.k8s.io" not found
I1010 09:24:48.438036    4686 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/10 09:24:48 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
I1010 09:24:48.445717    4686 http.go:37] curl https://ip.jsb.workers.dev
I1010 09:24:48.502260    4686 up.go:144] /logs/artifacts/ba083a13-29ab-11ec-b781-c649eef4635a/kops create cluster --name e2e-820e751628-53349.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=cilium-etcd --container-runtime=docker --admin-access 34.136.112.132/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones us-east-1a --master-size c5.large
I1010 09:24:48.518918    4725 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1010 09:24:48.519550    4725 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1010 09:24:48.563290    4725 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1010 09:24:49.052636    4725 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 47 lines ...

I1010 09:25:15.008542    4686 up.go:181] /logs/artifacts/ba083a13-29ab-11ec-b781-c649eef4635a/kops validate cluster --name e2e-820e751628-53349.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1010 09:25:15.022959    4745 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1010 09:25:15.023035    4745 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-820e751628-53349.test-cncf-aws.k8s.io

W1010 09:25:16.055210    4745 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-820e751628-53349.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:25:26.083719    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:25:36.129167    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:25:46.164265    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:25:56.191300    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:26:06.219221    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:26:16.246655    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:26:26.275055    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:26:36.318314    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:26:46.347153    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:26:56.374344    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:27:06.400779    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:27:16.430475    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:27:26.461235    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:27:36.487565    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:27:46.514560    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:27:56.553087    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:28:06.581237    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:28:16.611962    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:28:26.638822    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:28:36.666448    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:28:46.699813    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:28:56.731015    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:29:06.758746    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:29:16.787472    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:29:26.815461    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:29:36.856749    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:29:46.914644    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:29:56.955818    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:30:06.980990    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W1010 09:30:17.009141    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:30:28.560167    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:30:39.683276    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:30:50.674893    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:31:01.635166    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:31:13.040937    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:31:24.069877    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:31:35.089877    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:31:46.067423    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:31:56.987146    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:32:08.000771    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:32:19.074042    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:32:30.160854    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:32:41.929908    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:32:53.002999    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:33:04.067150    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:33:15.129110    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:33:26.192453    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:33:37.144781    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:33:48.117694    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:33:59.083835    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:34:10.094353    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:34:21.258756    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:34:32.129719    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:34:44.093399    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:34:55.508050    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:35:06.445592    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:35:17.380081    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:35:28.433680    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:35:39.402806    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:35:50.431001    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:36:01.646754    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:36:12.769634    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:36:23.794691    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:36:34.854454    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:36:46.900418    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:36:57.954363    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:37:08.965648    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:37:19.924213    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:37:30.933746    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:37:42.033021    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:37:53.139513    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:38:04.124821    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:38:15.227130    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:38:26.284387    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:38:37.250227    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:38:48.246171    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:38:59.235743    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:39:10.431112    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:39:21.494419    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:39:32.416796    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:39:43.640985    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:39:54.615311    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:40:05.675615    4745 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-us-east-1a	Master	c5.large	1	1	us-east-1a
nodes-us-east-1a	Node	t3.medium	4	4	us-east-1a

... skipping 9 lines ...
Machine	i-0fca46bee1d62cb7d				machine "i-0fca46bee1d62cb7d" has not yet joined cluster
Node	ip-172-20-34-98.ec2.internal			node "ip-172-20-34-98.ec2.internal" of role "master" is not ready
Pod	kube-system/cilium-rbwdf			system-node-critical pod "cilium-rbwdf" is pending
Pod	kube-system/coredns-5dc785954d-qrmjb		system-cluster-critical pod "coredns-5dc785954d-qrmjb" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-k2x4j	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-k2x4j" is pending

Validation Failed
W1010 09:40:16.617546    4745 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1010 09:40:26.623526    4686 dumplogs.go:40] /logs/artifacts/ba083a13-29ab-11ec-b781-c649eef4635a/kops toolbox dump --name e2e-820e751628-53349.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1010 09:40:26.641803    4756 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1010 09:40:26.641879    4756 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/10 09:40:33 Dumping node ip-172-20-34-98.ec2.internal
2021/10/10 09:40:35 dumping node not registered in kubernetes: 3.90.78.183
2021/10/10 09:40:35 Dumping node 3.90.78.183
... skipping 1209 lines ...
route-table:rtb-0bab17ce9f5180538	ok
vpc:vpc-0d87af969cb4c75a5	ok
dhcp-options:dopt-0e4eccb6cf1489156	ok
Deleted kubectl config for e2e-820e751628-53349.test-cncf-aws.k8s.io

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