This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-10-15 19:16
Elapsed18m0s
Revision
job-versionv1.23.0-alpha.3.354+55e1d2f9a73a0c
kubetest-version
revisionv1.23.0-alpha.3.354+55e1d2f9a73a0c

Test Failures


kubetest Up 15m32s

kops validate cluster failed: error during /tmp/kops2931731129/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Error lines from build-log.txt

Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
fatal: not a git repository (or any of the parent directories): .git
+ WRAPPED_COMMAND_PID=31
+ wait 31
+ /workspace/scenarios/kubernetes_e2e.py --cluster=e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --deployment=kops --env=KOPS_ARCH=amd64 --env=KUBE_SSH_USER=ec2-user --env=KOPS_RUN_TOO_NEW_VERSION=1 --extract=ci/latest --ginkgo-parallel --kops-image=309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --kops-args=--master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --kops-overrides=spec.docker.selinuxEnabled=true --kops-priority-path=/workspace/kubernetes/platforms/linux/amd64 --kops-ssh-user=ec2-user --kops-version=https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt --provider=aws '--test_args=--ginkgo.focus=\[sig-storage\].*\[Slow\] --ginkgo.skip=\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8' --timeout=120m
starts with local mode
Environment:
ARTIFACTS=/logs/artifacts
... skipping 158 lines ...
md5sum(kubernetes-test-linux-amd64.tar.gz)=401b65cbd03b21ddcf3298ae5abc51f1
sha512sum(kubernetes-test-linux-amd64.tar.gz)=d02ac5a4b2ed6f209fe009164e37366c5963b585565fc8b7be5f96b5e478c48b7ea75a5ff619f37cf3be651f789a6f00ccd39680872629c6a7cea644bc06a5ee

Extracting /workspace/kubernetes/test/kubernetes-test-linux-amd64.tar.gz into /workspace/kubernetes/platforms/linux/amd64
2021/10/15 19:16:42 process.go:155: Step './get-kube.sh' finished in 28.685398955s
2021/10/15 19:16:42 process.go:153: Running: /tmp/kops2931731129/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
Error: cluster not found "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/15 19:16:42 process.go:155: Step '/tmp/kops2931731129/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 552.416799ms
2021/10/15 19:16:42 util.go:42: curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/15 19:16:42 kops.go:514: 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
2021/10/15 19:16:42 util.go:68: curl https://ip.jsb.workers.dev
2021/10/15 19:16:42 kops.go:439: Using external IP for admin access: 35.232.18.61/32
2021/10/15 19:16:42 process.go:153: Running: /tmp/kops2931731129/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.354+55e1d2f9a73a0c --admin-access 35.232.18.61/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes
I1015 19:16:42.786619     989 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I1015 19:16:42.815490     989 create_cluster.go:838] Using SSH public key: /workspace/.ssh/kube_aws_rsa.pub
I1015 19:16:43.423061     989 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

2021/10/15 19:17:07 process.go:155: Step '/tmp/kops2931731129/kops create cluster --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --ssh-public-key /workspace/.ssh/kube_aws_rsa.pub --node-count 4 --node-volume-size 48 --master-volume-size 48 --master-count 1 --zones eu-central-1b --master-size c5.large --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.23.0-alpha.3.354+55e1d2f9a73a0c --admin-access 35.232.18.61/32 --image 309956199498/RHEL-7.8_HVM_GA-20200225-x86_64-1-Hourly2-GP2 --cloud aws --master-image=137112412989/amzn2-ami-hvm-2.0.20200617.0-x86_64-gp2 --override spec.docker.selinuxEnabled=true,cluster.spec.nodePortAccess=0.0.0.0/0 --yes' finished in 25.057575482s
2021/10/15 19:17:07 process.go:153: Running: /tmp/kops2931731129/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m
I1015 19:17:07.842206    1009 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

W1015 19:17:09.071480    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1015 19:17:19.104708    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:17:29.152476    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:17:39.191416    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:17:49.228567    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
W1015 19:17:59.248241    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1015 19:18:09.281436    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
W1015 19:18:19.314842    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:18:29.362235    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:18:39.394648    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:18:49.428494    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:18:59.463523    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:19:09.503441    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:19:19.539240    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
W1015 19:19:29.559634    1009 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-kops-aws-k8s-storage-selinux.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-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:19:39.593725    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:19:49.623919    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:19:59.655971    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:20:09.690127    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:20:19.724476    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:20:29.759561    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:20:39.795319    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

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
W1015 19:20:49.830196    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 8 lines ...
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Node	ip-172-20-43-80.eu-central-1.compute.internal	master "ip-172-20-43-80.eu-central-1.compute.internal" is missing kube-controller-manager pod
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:21:02.701605    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:21:14.836419    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:21:26.836824    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:21:38.813643    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:21:50.723126    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:22:02.746792    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:22:14.628090    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:22:26.602521    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:22:38.511250    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:22:50.574368    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:23:02.605817    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:23:14.656500    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:23:26.542200    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:23:38.660609    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:23:50.768479    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:24:02.910329    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:24:14.978023    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:24:27.038229    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:24:39.049285    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:24:51.046141    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:25:03.464751    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:25:15.537691    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:25:27.460994    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:25:39.495662    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:25:51.388972    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:26:03.280899    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:26:15.227842    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:26:27.240226    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:26:39.340338    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:26:51.392339    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:27:03.511923    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:27:15.546784    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:27:27.569522    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:27:39.538699    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:27:51.603245    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:28:03.629884    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:28:15.645390    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:28:27.656441    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:28:39.729767    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:28:51.798875    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:29:04.274592    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:29:16.275254    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:29:28.228332    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:29:40.335456    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:29:52.398513    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:30:04.562289    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:30:16.624481    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:30:28.669784    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:30:40.807650    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:30:52.973429    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:31:05.420605    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:31:17.325860    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:31:29.476648    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:31:41.529276    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:31:53.364597    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-central-1b	Master	c5.large	1	1	eu-central-1b
nodes-eu-central-1b	Node	t3.medium	4	4	eu-central-1b

... skipping 7 lines ...
Machine	i-043a41bbadc8c1935				machine "i-043a41bbadc8c1935" has not yet joined cluster
Machine	i-0baf0be8a367a6232				machine "i-0baf0be8a367a6232" has not yet joined cluster
Machine	i-0e7c010da8cf38f37				machine "i-0e7c010da8cf38f37" has not yet joined cluster
Pod	kube-system/coredns-6c8944dbdc-r6bwr		system-cluster-critical pod "coredns-6c8944dbdc-r6bwr" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-tkxp9	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-tkxp9" is pending

Validation Failed
W1015 19:32:05.477394    1009 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
2021/10/15 19:32:15 process.go:155: Step '/tmp/kops2931731129/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m' finished in 15m7.664046s
2021/10/15 19:32:15 process.go:153: Running: kubectl -n kube-system get pods -ojson
2021/10/15 19:32:15 process.go:153: Running: /tmp/kops2931731129/kops toolbox dump --name e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io -ojson
I1015 19:32:15.552647    1024 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
2021/10/15 19:32:17 process.go:155: Step 'kubectl -n kube-system get pods -ojson' finished in 1.77897098s
2021/10/15 19:32:17 process.go:153: Running: kubectl -n kube-system logs --all-containers coredns-6c8944dbdc-r6bwr
... skipping 40 lines ...
2021/10/15 19:32:31 dump.go:413: Running SSH command: sudo cat /var/log/etcd.log
2021/10/15 19:32:31 dump.go:413: Running SSH command: sudo cat /var/log/etcd-events.log
2021/10/15 19:32:31 dump.go:413: Running SSH command: sudo cat /var/log/kube-proxy.log
2021/10/15 19:32:32 dump.go:413: Running SSH command: sudo cat /var/log/cloud-init-output.log
2021/10/15 19:32:32 dump.go:129: dumping node not registered in kubernetes: 18.156.7.55
2021/10/15 19:32:32 dump.go:163: Dumping node 18.156.7.55
2021/10/15 19:32:32 dump.go:132: error dumping node 18.156.7.55: could not connect: unable to SSH to "18.156.7.55": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/15 19:32:32 dump.go:129: dumping node not registered in kubernetes: 18.197.57.3
2021/10/15 19:32:32 dump.go:163: Dumping node 18.197.57.3
2021/10/15 19:32:33 dump.go:132: error dumping node 18.197.57.3: could not connect: unable to SSH to "18.197.57.3": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/15 19:32:33 dump.go:129: dumping node not registered in kubernetes: 3.121.186.184
2021/10/15 19:32:33 dump.go:163: Dumping node 3.121.186.184
2021/10/15 19:32:34 dump.go:132: error dumping node 3.121.186.184: could not connect: unable to SSH to "3.121.186.184": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/15 19:32:34 dump.go:129: dumping node not registered in kubernetes: 18.197.149.42
2021/10/15 19:32:34 dump.go:163: Dumping node 18.197.149.42
2021/10/15 19:32:35 dump.go:132: error dumping node 18.197.149.42: could not connect: unable to SSH to "18.197.149.42": ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
2021/10/15 19:32:35 process.go:153: Running: /tmp/kops2931731129/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io
I1015 19:32:35.506407    1141 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
NAME							CLOUD	ZONES
e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io	aws	eu-central-1b
2021/10/15 19:32:36 process.go:155: Step '/tmp/kops2931731129/kops get clusters e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io' finished in 630.947239ms
2021/10/15 19:32:36 process.go:153: Running: /tmp/kops2931731129/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes
... skipping 198 lines ...
dhcp-options:dopt-0d54beacb71bce7d6	ok
Deleted kubectl config for e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io

Deleted cluster: "e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io"
2021/10/15 19:34:07 process.go:155: Step '/tmp/kops2931731129/kops delete cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --yes' finished in 1m31.383669233s
2021/10/15 19:34:07 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/10/15 19:34:07 main.go:331: Something went wrong: starting e2e cluster: kops validate cluster failed: error during /tmp/kops2931731129/kops validate cluster e2e-kops-aws-k8s-storage-selinux.test-cncf-aws.k8s.io --wait 15m: exit status 1
Traceback (most recent call last):
  File "/workspace/scenarios/kubernetes_e2e.py", line 723, in <module>
    main(parse_args())
  File "/workspace/scenarios/kubernetes_e2e.py", line 569, in main
    mode.start(runner_args)
  File "/workspace/scenarios/kubernetes_e2e.py", line 228, in start
... skipping 9 lines ...