Description of problem: Attempting to follow https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/ does not give me the node showing up in the kubectl get nodes output. Part of the problem is that KUBELET_API_SERVER seems no longer supported: https://github.com/kubernetes/website/issues/7521 It might be useful to do something similar to https://github.com/kubernetes/kubernetes/pull/40050/files -- ship some example /etc/kubernetes/kubelet.kubeconfig, put # Edit the kubelet.kubeconfig to have correct cluster server address # KUBELET_KUBECONFIG=/etc/kubernetes/kubelet.kubeconfig into /etc/kubernetes/kubelet and change /usr/lib/systemd/system/kubelet.service to use $KUBELET_KUBECONFIG instead of $KUBELET_API_SERVER Version-Release number of selected component (if applicable): kubernetes-node-1.9.1-5.fc27.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. Attempt to do simple all-on-one Kubernetes setup. 2. Follow https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/ 3. Try to get the node (which can be the same machine as the master) to show up in kubectl get nodes output. Actual results: The --api-servers is no longer supported, the use of $KUBELET_API_SERVER in /usr/lib/systemd/system/kubelet.service is confusing, kubelet.kubeconfig which seems to be needed now is not shipped in kubernetes-node. Expected results: It's very simple to make the node "attach" to the master because kubelet.kubeconfig is shipped in the package and all it takes is to put in the correct master address and uncomment the KUBELET_KUBECONFIG line in /etc/kubernetes/kubelet. Additional info:
I've now filed https://github.com/kubernetes/contrib/pull/2863 which is where kubernetes-node gets its .service content from. If this gets merged, /etc/kubernetes/kubelet.kubeconfig might need to get added to %files.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.