Join GitHub today
Kubelet won't read apiserver from kubeconfig #36745
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):
What keywords did you search in Kubernetes issues before filing this one?
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Kubernetes version (use
The error in kubelet log is:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
This was referenced
Nov 14, 2016
@dims That issue is related and seems to suggest there is no bug. But I am still encountering the issue where Kubelet won't actually communicate with the server located in my kubeconfig. All that bug does is tolerate the absence of kubeconfig (and waits for it to be created, or die if --require-kubeconfig is set).
I recall agreeing to that, but I don't know that it was actually changed
On Nov 16, 2016, at 1:51 AM, Jordan Liggitt email@example.com
I repeated this error in v1.4.5
If I specify --kubeconfig with --api-servers, it reports
If I specify --kubeconfig only and omit --api-servers, it reports
While I did not even saw this log
I see the same behavior on 1.5.2 (node is on same box as api-server, all insecure mode.)
Tested in 1.6.1, --require-kubeconfig is still required to make this work.
We need to be careful, as api-server in this version is being deprecated (still works, but issues a WARNING about this deprecation) and require-kubeconfig is not clear about being used also for api-server connection.
Is there any plan to make require-kubeconfig default to true in next versions?
Actually, I should speak more precisely. In 1.7, the plan is to remove --api-servers and make the presence of the --kubeconfig flag determine whether an API connection is made. The presence of --kubeconfig will require the specified file and the absence of --kubeconfig will mean the kubelet is in standalone mode.