This job view page is being replaced by Spyglass soon. Check out the new job view.
PRolemarkus: Enable IRSA for CCM
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-07-04 19:25
Elapsed23m54s
Revision584e088543dcd3b1a3c0ff58ded2892ea0aa0101
Refs 11818

No Test Failures!


Error lines from build-log.txt

... skipping 486 lines ...
I0704 19:30:11.041596    4246 up.go:43] Cleaning up any leaked resources from previous cluster
I0704 19:30:11.041674    4246 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0704 19:30:11.058547   11777 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0704 19:30:11.059019   11777 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io" not found
W0704 19:30:11.563338    4246 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0704 19:30:11.563447    4246 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --yes
I0704 19:30:11.580991   11788 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0704 19:30:11.581327   11788 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io" not found
I0704 19:30:12.056603    4246 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/07/04 19:30:12 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
I0704 19:30:12.064743    4246 http.go:37] curl https://ip.jsb.workers.dev
I0704 19:30:12.163922    4246 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.0-beta.0 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210621 --channel=alpha --networking=kubenet --container-runtime=containerd --override=cluster.spec.cloudControllerManager.cloudProvider=aws --admin-access 35.184.205.92/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones eu-central-1a --master-size c5.large
I0704 19:30:12.183771   11798 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0704 19:30:12.183882   11798 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
I0704 19:30:12.231884   11798 create_cluster.go:739] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0704 19:30:12.758333   11798 new_cluster.go:1054]  Cloud Provider ID = aws
... skipping 31 lines ...

I0704 19:30:38.091081    4246 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0704 19:30:38.108308   11818 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0704 19:30:38.108471   11818 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

W0704 19:30:39.360736   11818 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-cbaca3167c-2049b.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
W0704 19:30:49.407239   11818 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
W0704 19:30:59.448000   11818 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
W0704 19:31:09.479066   11818 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
W0704 19:31:19.508740   11818 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
W0704 19:31:29.542606   11818 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
W0704 19:31:39.572433   11818 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
W0704 19:31:49.602328   11818 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
W0704 19:31:59.630971   11818 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
W0704 19:32:09.663824   11818 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
W0704 19:32:19.710604   11818 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
W0704 19:32:29.756691   11818 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
W0704 19:32:39.788001   11818 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
W0704 19:32:49.831912   11818 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
W0704 19:32:59.878612   11818 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
W0704 19:33:09.907901   11818 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
W0704 19:33:19.939245   11818 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
W0704 19:33:29.973899   11818 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
W0704 19:33:40.002865   11818 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
W0704 19:33:50.034532   11818 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
W0704 19:34:00.085390   11818 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
W0704 19:34:10.135664   11818 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
W0704 19:34:20.164807   11818 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
W0704 19:34:30.207797   11818 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 8 lines ...
Machine	i-0eb4feabfb9d5e056				machine "i-0eb4feabfb9d5e056" has not yet joined cluster
Machine	i-0f14a340569d68c36				machine "i-0f14a340569d68c36" has not yet joined cluster
Node	ip-172-20-40-69.eu-central-1.compute.internal	node "ip-172-20-40-69.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:34:43.124350   11818 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 8 lines ...
Machine	i-0eb4feabfb9d5e056				machine "i-0eb4feabfb9d5e056" has not yet joined cluster
Machine	i-0f14a340569d68c36				machine "i-0f14a340569d68c36" has not yet joined cluster
Node	ip-172-20-40-69.eu-central-1.compute.internal	node "ip-172-20-40-69.eu-central-1.compute.internal" of role "master" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:34:55.246988   11818 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 9 lines ...
Machine	i-0f14a340569d68c36				machine "i-0f14a340569d68c36" has not yet joined cluster
Node	ip-172-20-40-69.eu-central-1.compute.internal	node "ip-172-20-40-69.eu-central-1.compute.internal" of role "master" is not ready
Node	ip-172-20-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:35:07.243062   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending
Pod	kube-system/ebs-csi-node-gpvtg			system-node-critical pod "ebs-csi-node-gpvtg" is pending

Validation Failed
W0704 19:35:19.219154   11818 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-52-158.eu-central-1.compute.internal				node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal				node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k					system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending
Pod	kube-system/kube-proxy-ip-172-20-52-158.eu-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-52-158.eu-central-1.compute.internal" is pending

Validation Failed
W0704 19:35:31.141632   11818 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-57-109.eu-central-1.compute.internal				node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn				system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k					system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending
Pod	kube-system/kube-proxy-ip-172-20-35-196.eu-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-35-196.eu-central-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-42-101.eu-central-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-42-101.eu-central-1.compute.internal" is pending

Validation Failed
W0704 19:35:43.086695   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:35:55.101960   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:36:07.071641   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:36:19.102637   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:36:31.124352   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:36:43.088861   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:36:55.091936   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:37:07.069991   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:37:19.239334   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:37:31.197014   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:37:43.211167   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:37:55.290639   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:38:07.367353   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:38:19.440917   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:38:31.402152   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:38:43.793239   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:38:55.717721   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:39:07.820923   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:39:19.786787   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:39:31.870716   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:39:43.930504   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:39:55.928523   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:40:07.889863   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:40:19.839502   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:40:31.821489   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:40:43.770842   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:40:55.677807   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:41:07.728113   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:41:19.706963   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:41:31.634248   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:41:43.703478   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:41:55.657598   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:42:09.716013   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:42:21.678203   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:42:34.035598   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:42:45.929420   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:42:57.859528   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:43:09.848931   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:43:21.722911   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:43:33.725076   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:43:45.863173   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:43:57.855628   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:44:09.874306   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:44:21.843735   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:44:33.854032   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:44:46.088425   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:44:58.053066   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:45:10.161629   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:45:22.193842   11818 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-42-101.eu-central-1.compute.internal	node "ip-172-20-42-101.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-52-158.eu-central-1.compute.internal	node "ip-172-20-52-158.eu-central-1.compute.internal" of role "node" is not ready
Node	ip-172-20-57-109.eu-central-1.compute.internal	node "ip-172-20-57-109.eu-central-1.compute.internal" of role "node" is not ready
Pod	kube-system/coredns-autoscaler-6f594f4c58-6bmvn	system-cluster-critical pod "coredns-autoscaler-6f594f4c58-6bmvn" is pending
Pod	kube-system/coredns-f45c4bf76-rqm2k		system-cluster-critical pod "coredns-f45c4bf76-rqm2k" is pending

Validation Failed
W0704 19:45:34.159410   11818 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I0704 19:45:44.166997    4246 dumplogs.go:38] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0704 19:45:44.186760   11829 featureflag.go:167] FeatureFlag "SpecOverrideFlag"=true
I0704 19:45:44.186882   11829 featureflag.go:167] FeatureFlag "AlphaAllowGCE"=true
2021/07/04 19:45:54 Dumping node ip-172-20-35-196.eu-central-1.compute.internal
2021/07/04 19:45:59 Dumping node ip-172-20-40-69.eu-central-1.compute.internal
2021/07/04 19:46:05 Dumping node ip-172-20-42-101.eu-central-1.compute.internal
... skipping 1438 lines ...
route-table:rtb-05a3f6b6c40de0603	ok
vpc:vpc-0d1f8653c326d6ad1	ok
dhcp-options:dopt-01147930fdb7427e5	ok
Deleted kubectl config for e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io

Deleted cluster: "e2e-cbaca3167c-2049b.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...