search

kubernetes-retired / contrib

[EOL] This is a place for various components in the Kubernetes ecosystem that aren't part of the Kubernetes core.
Apache License 2.0
2.46k stars 1.68k forks source link

kubelet Error: unknown flag: --api-servers #2830

Closed maltris closed 6 years ago

maltris commented 6 years ago

OS:

Fedora 27 Server
Jan 20 18:41:13 kube2 systemd[1]: Started Kubernetes Kubelet Server.
Jan 20 18:41:13 kube2 kubelet[18407]: Error: unknown flag: --api-servers
Jan 20 18:41:13 kube2 kubelet[18407]: The kubelet binary is responsible for maintaining a set of containers on a
Jan 20 18:41:13 kube2 kubelet[18407]:   particular node. It syncs data from a variety of sources including a
Jan 20 18:41:13 kube2 kubelet[18407]:   Kubernetes API server, an etcd cluster, HTTP endpoint or local file. It then
Jan 20 18:41:13 kube2 kubelet[18407]:   queries Docker to see what is currently running.  It synchronizes the
Jan 20 18:41:13 kube2 kubelet[18407]:   configuration data, with the running set of containers by starting or stopping
Jan 20 18:41:13 kube2 kubelet[18407]:   Docker containers.
Jan 20 18:41:13 kube2 kubelet[18407]: Usage:
Jan 20 18:41:13 kube2 kubelet[18407]:   kubelet [flags]
Jan 20 18:41:13 kube2 kubelet[18407]: Available Flags:
Jan 20 18:41:13 kube2 kubelet[18407]:       --address 0.0.0.0                                                                              
Jan 20 18:41:13 kube2 kubelet[18407]:       --allow-privileged                                                                             
Jan 20 18:41:13 kube2 kubelet[18407]:       --allow-verification-with-non-compliant-keys                                                   
Jan 20 18:41:13 kube2 kubelet[18407]:       --alsologtostderr                                                                              
Jan 20 18:41:13 kube2 kubelet[18407]:       --anonymous-auth                                                                               
Jan 20 18:41:13 kube2 kubelet[18407]:       --application-metrics-count-limit int                                                          
Jan 20 18:41:13 kube2 kubelet[18407]:       --authentication-token-webhook                                                                 
Jan 20 18:41:13 kube2 kubelet[18407]:       --authentication-token-webhook-cache-ttl duration                                              
Jan 20 18:41:13 kube2 kubelet[18407]:       --authorization-mode string                                                                    
Jan 20 18:41:13 kube2 kubelet[18407]:       --authorization-webhook-cache-authorized-ttl duration                                          
Jan 20 18:41:13 kube2 kubelet[18407]:       --authorization-webhook-cache-unauthorized-ttl duration                                        
Jan 20 18:41:13 kube2 kubelet[18407]:       --azure-container-registry-config string                                                       
Jan 20 18:41:13 kube2 kubelet[18407]:       --boot-id-file string                                                                          
Jan 20 18:41:13 kube2 kubelet[18407]:       --bootstrap-checkpoint-path string                                                             
Jan 20 18:41:13 kube2 kubelet[18407]:       --bootstrap-kubeconfig string                                                                  
Jan 20 18:41:13 kube2 kubelet[18407]:       --cadvisor-port int32                                                                          
Jan 20 18:41:13 kube2 kubelet[18407]:       --cert-dir string 
kubelet --version
Kubernetes v1.9.1

After commenting out the following in /etc/kubernetes/kubelet it was fine:

KUBELET_API_SERVER="--api-servers=https://kube1:443"

Found a related issue here: https://github.com/coreos/coreos-kubernetes/issues/785

According to /etc/kubernetes/kubelet the "--kubeconfig" parameter is already set anyway:

KUBELET_ARGS="--kubeconfig=/etc/kubernetes/kubelet.kubeconfig [...]"
fejta-bot commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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

k8s-ci-robot commented 5 years ago

@app63: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/kubernetes/contrib/issues/2830#issuecomment-454658186): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.