This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
Cluster with TLS bootstrap disabled fails to start self-hosted Kubelet #1525
Labels
area/kubernetes
Core Kubernetes stuff
area/updates
Items related to updates
bug
Something isn't working
platform/aws
AWS-related
platform/bare-metal
Bare-metal-related
platform/packet
Packet-related
Comments
surajssd
added
bug
|
Related: #1468 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The self-hosted kubelet has a dependency on a file to exist at
/var/lib/kubelet/kubeconfig. This was added during the cert rotation feature.On a cluster that has TLS bootstrap disabled there is no file at
/var/lib/kubelet/kubeconfigso the self-hosted kubelet fails to come up. The current workaround is to create an empty file at/var/lib/kubelet/kubeconfig. The ideal solution is that we create a empty file by default ifenable_tls_bootstrapis set to false.And the best solution is to deprecate
enable_tls_bootstrapwith an upgrade paths that have disabledenable_tls_bootstrap.The text was updated successfully, but these errors were encountered: