remote error: tls: internal error

[metanovii]

Problem in fresh cluster

root@qa-control-plane-ndh9w:/etc/kubernetes# KUBECONFIG=admin.conf kubectl get pods -A
NAMESPACE     NAME                                             READY   STATUS             RESTARTS      AGE
kube-system   etcd-qa-control-plane-ndh9w                      1/1     Running            1 (53s ago)   16m
kube-system   kube-apiserver-qa-control-plane-ndh9w            1/1     Running            1 (53s ago)   16m
kube-system   kube-controller-manager-qa-control-plane-ndh9w   0/1     CrashLoopBackOff   13 (9s ago)   16m
kube-system   kube-scheduler-qa-control-plane-ndh9w            1/1     Running            1 (53s ago)   16m
root@qa-control-plane-ndh9w:/etc/kubernetes# KUBECONFIG=admin.conf kubectl -n kube-system logs -f kube-controller-manager-qa-control-plane-ndh9w
Error from server: Get "https://qa-control-plane-ndh9w:10250/containerLogs/kube-system/kube-controller-manager-qa-control-plane-ndh9w/kube-controller-manager?follow=true": remote error: tls: internal error

What am I doing wrong?

[benedikt-bartscher]

I get the same error while following quickstart.md. Kubelet log:

Sep 21 17:10:08 cluster-api-mgmt-control-plane-szj2m kubelet[749]: I0921 17:10:08.336189     749 log.go:194] http: TLS handshake error from 127.0.0.1:56340: no serving certificate available for the kubelet

[batistein]

please check the logs in /var/log/cloud-init-output.log To see the logs of a pod on the control-plane do cat /var/log/pods/...

[batistein]

no serving certificate available for the kubelet

Can you please check the output of kubectl get csr -A

[guettli]

I am closing this issue, since we go no further feedback.

Please open a new issue, if something is not working with the current beta.32 release.