Issue with k8s.io/docs/getting-started-guides/fedora/fedora_manual_config/

[adelton]

This is a...

• Feature Request
• Bug Report

Problem:

The page https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/ says:

    Edit /etc/kubernetes/kubelet to appear as such:

###
# Kubernetes kubelet (node) config

# The address for the info server to serve on (set to 0.0.0.0 or "" for all interfaces)
KUBELET_ADDRESS="--address=0.0.0.0"

# You may leave this blank to use the actual hostname
KUBELET_HOSTNAME="--hostname-override=fed-node"

# location of the api-server
KUBELET_API_SERVER="--api-servers=http://fed-master:8080"

# Add your own!
#KUBELET_ARGS=""

When I do that, attempt to start the kubelet service seemingly passes but systemctl status kubelet reports

Failed to start Kubernetes Kubelet Server.

and journalctl _COMM=kubelet -l says

Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]: Error: unknown flag: --api-servers
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]: The kubelet binary is responsible for maintaining a set of containers on a
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]:   particular node. It syncs data from a variety of sources including a
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]:   Kubernetes API server, an etcd cluster, HTTP endpoint or local file. It then
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]:   queries Docker to see what is currently running.  It synchronizes the
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]:   configuration data, with the running set of containers by starting or stopping
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]:   Docker containers.
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]: Usage:
Feb 26 12:34:33 kubernetes-cri-o.example.test kubelet[3707]:   kubelet [flags]
[...]

Proposed Solution:

Update the documentation to match the current software.

Page to Update:
https://kubernetes.io/docs/getting-started-guides/fedora/fedora_manual_config/

Kubernetes Version:

# rpm -qa 'kubernetes*'
kubernetes-client-1.9.1-5.fc27.x86_64
kubernetes-node-1.9.1-5.fc27.x86_64
kubernetes-master-1.9.1-5.fc27.x86_64
kubernetes-1.9.1-5.fc27.x86_64

[adelton]

I was able to make things work to the point where the node shows up in the kubectl get nodes by creating /etc/kubernetes/kubelet.kubeconfig with content

apiVersion: v1
kind: Config
clusters:
  - cluster:
      server: http://kubernetes-cri-o.example.test:8080/
    name: local
contexts:
  - context:
      cluster: local
    name: local
current-context: local

and adding --kubeconfig=/etc/kubernetes/kubelet.kubeconfig to KUBELET_ARGS in /etc/kubernetes/kubelet.

I took inspiration from https://github.com/kubernetes/kubernetes/pull/40050/files. Maybe the Fedora packaging ought to be changed to ship an example kubelet.kubeconfig file and use the KUBELET_KUBECONFIG environment variable?

[adelton]

I've now filed https://bugzilla.redhat.com/show_bug.cgi?id=1549151 to improve the packaging in Fedora.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close