This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-05-05 04:20
Elapsed24m51s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 125 lines ...
I0505 04:21:07.901720    4058 up.go:43] Cleaning up any leaked resources from previous cluster
I0505 04:21:07.901754    4058 dumplogs.go:38] /logs/artifacts/25e3e182-ad59-11eb-996d-76c2105c4a5f/kops toolbox dump --name e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user core
I0505 04:21:07.918900    4078 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0505 04:21:07.919011    4078 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io" not found
W0505 04:21:08.432758    4058 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0505 04:21:08.432814    4058 down.go:48] /logs/artifacts/25e3e182-ad59-11eb-996d-76c2105c4a5f/kops delete cluster --name e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io --yes
I0505 04:21:08.447632    4088 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0505 04:21:08.447726    4088 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io" not found
I0505 04:21:08.969073    4058 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/05/05 04:21:08 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
I0505 04:21:08.977598    4058 http.go:37] curl https://ip.jsb.workers.dev
I0505 04:21:09.090076    4058 up.go:143] /logs/artifacts/25e3e182-ad59-11eb-996d-76c2105c4a5f/kops create cluster --name e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.18.18 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=075585003325/Flatcar-stable-2765.2.3-hvm --channel=alpha --networking=kopeio --container-runtime=containerd --admin-access 35.192.90.167/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large
I0505 04:21:09.105656    4098 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0505 04:21:09.105763    4098 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
I0505 04:21:09.151816    4098 create_cluster.go:730] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0505 04:21:09.652410    4098 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 44 lines ...

I0505 04:21:36.258922    4058 up.go:179] /logs/artifacts/25e3e182-ad59-11eb-996d-76c2105c4a5f/kops validate cluster --name e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io --count 10 --wait 20m0s
I0505 04:21:36.277414    4119 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0505 04:21:36.277543    4119 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io

W0505 04:21:37.625543    4119 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W0505 04:21:47.661230    4119 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:21:57.723198    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
W0505 04:22:07.755795    4119 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:22:17.786154    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:22:27.834700    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:22:37.865566    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:22:47.912019    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:22:57.940679    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:23:07.988239    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:23:18.064002    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:23:28.100744    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:23:38.405473    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:23:48.435760    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:23:58.467018    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:24:08.502816    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:24:18.563039    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:24:28.610113    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:24:38.650767    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:24:48.682314    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
W0505 04:24:58.719901    4119 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:25:08.871745    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
W0505 04:25:18.903865    4119 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:25:28.935905    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:25:38.976437    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:25:49.009079    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:25:59.041873    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:26:09.076033    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:26:19.130309    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0505 04:26:29.187877    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 11 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kopeio-networking-agent-8wtp8		system-node-critical pod "kopeio-networking-agent-8wtp8" is pending
Pod	kube-system/kopeio-networking-agent-h8npb		system-node-critical pod "kopeio-networking-agent-h8npb" is pending
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:26:42.053939    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 15 lines ...
Pod	kube-system/kopeio-networking-agent-blhnl		system-node-critical pod "kopeio-networking-agent-blhnl" is pending
Pod	kube-system/kopeio-networking-agent-h8npb		system-node-critical pod "kopeio-networking-agent-h8npb" is pending
Pod	kube-system/kopeio-networking-agent-mp658		system-node-critical pod "kopeio-networking-agent-mp658" is pending
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:26:54.011726    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 15 lines ...
Pod	kube-system/kopeio-networking-agent-blhnl		system-node-critical pod "kopeio-networking-agent-blhnl" is not ready (networking-agent)
Pod	kube-system/kopeio-networking-agent-h8npb		system-node-critical pod "kopeio-networking-agent-h8npb" is pending
Pod	kube-system/kopeio-networking-agent-mp658		system-node-critical pod "kopeio-networking-agent-mp658" is pending
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:27:05.972655    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 14 lines ...
Node	ip-172-20-61-242.eu-central-1.compute.internal				node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kopeio-networking-agent-h8npb				system-node-critical pod "kopeio-networking-agent-h8npb" is not ready (networking-agent)
Pod	kube-system/kube-dns-677d5df9b4-nbnm5					system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf			system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-111.eu-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-111.eu-central-1.compute.internal" is pending

Validation Failed
W0505 04:27:17.970053    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 13 lines ...
Node	ip-172-20-61-111.eu-central-1.compute.internal				node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal				node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5					system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf			system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending
Pod	kube-system/kube-proxy-ip-172-20-61-242.eu-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-61-242.eu-central-1.compute.internal" is pending

Validation Failed
W0505 04:27:29.892795    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:27:42.913594    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:27:54.924405    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:28:06.934617    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:28:18.853380    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:28:30.774965    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:28:42.955616    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:28:55.024905    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:29:07.027550    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:29:19.047265    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:29:30.956998    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:29:42.913321    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:29:54.955526    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:30:06.927196    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:30:19.055198    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:30:31.028735    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:30:43.296234    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:30:55.251321    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:31:07.258869    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:31:19.314960    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:31:31.551647    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:31:43.486304    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:31:55.501339    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:32:07.436416    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:32:19.432090    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:32:31.558326    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:32:43.445050    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:32:55.399284    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:33:07.449436    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:33:19.327279    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:33:31.520874    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:33:43.458149    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:33:55.392997    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:34:07.455175    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:34:19.445728    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:34:31.386245    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:34:43.658821    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:34:55.694882    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:35:07.903609    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:35:19.983231    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:35:31.989788    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:35:43.991105    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:35:55.977359    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:36:08.255906    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:36:20.154503    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:36:32.164497    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:36:44.191790    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:36:56.163220    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:37:08.250683    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:37:20.224999    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:37:32.108398    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:37:44.061791    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:37:56.029376    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:38:08.301275    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:38:20.416794    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:38:32.458268    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:38:44.845720    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:38:56.910133    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:39:08.890189    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:39:20.904901    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:39:33.991541    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:39:45.904801    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:39:57.855641    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:40:09.903775    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:40:21.797558    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:40:33.968900    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:40:45.967356    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:40:57.936087    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:41:09.916550    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:41:21.930077    4119 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1a	Master	c5.large	1	1	eu-central-1a
nodes-eu-central-1a	Node	t3.medium	4	4	eu-central-1a

... skipping 12 lines ...
Node	ip-172-20-47-218.eu-central-1.compute.internal		node "ip-172-20-47-218.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-111.eu-central-1.compute.internal		node "ip-172-20-61-111.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-61-242.eu-central-1.compute.internal		node "ip-172-20-61-242.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/kube-dns-677d5df9b4-nbnm5			system-cluster-critical pod "kube-dns-677d5df9b4-nbnm5" is pending
Pod	kube-system/kube-dns-autoscaler-7f87957f46-vd2pf	system-cluster-critical pod "kube-dns-autoscaler-7f87957f46-vd2pf" is pending

Validation Failed
W0505 04:41:33.920261    4119 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0505 04:41:43.925493    4058 dumplogs.go:38] /logs/artifacts/25e3e182-ad59-11eb-996d-76c2105c4a5f/kops toolbox dump --name e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user core
I0505 04:41:43.941841    4129 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0505 04:41:43.942197    4129 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
2021/05/05 04:41:53 Dumping node ip-172-20-40-218.eu-central-1.compute.internal
2021/05/05 04:41:57 Dumping node ip-172-20-44-197.eu-central-1.compute.internal
2021/05/05 04:42:02 Dumping node ip-172-20-47-218.eu-central-1.compute.internal
... skipping 1382 lines ...
route-table:rtb-0da71bf3fc1b06190	ok
vpc:vpc-09059b10ff1bc6acb	ok
dhcp-options:dopt-0359774bd1d08ab77	ok
Deleted kubectl config for e2e-ea3b77a2f1-318ad.test-cncf-aws.k8s.io

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