Minikube: apiserver.Features.EnableSwaggerUI causes kube-proxy failure

Created on 16 May 2018 · 5Comments · Source: kubernetes/minikube

Environment

Minikube version:0.26.0
OS:Ubuntu 16.04 LTS
VM Driver: Virtualbox
ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
Install tools: apt-get(by ubuntu ppa)
Others:

What happened:
i have follow the issue https://github.com/kubernetes/minikube/issues/1509, to use command to
start swagger-ui

minikube start --extra-config=apiserver.Features.EnableSwaggerUI=true

but the error Message is like this

 ~ sudo minikube start --extra-config=apiserver.Features.EnableSwaggerUI=true
[sudo] ray 的密码： 
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
^[2

E0516 17:09:51.222767    6600 start.go:281] Error restarting cluster:  restarting kube-proxy: waiting for kube-proxy to be up for configmap update: timed out waiting for the condition

so how can i use swagger-ui to check api usage on minikube?

capiserver kinbug lifecyclrotten

Source

ray1888

👍1

Most helpful comment

The following workaround can fix it if you do not use Localkube:

$ minikube start  --extra-config=apiserver.enable-swagger-ui=true

kairen on 18 May 2018

👍8 ❤1

All 5 comments

The following workaround can fix it if you do not use Localkube:

$ minikube start  --extra-config=apiserver.enable-swagger-ui=true

kairen on 18 May 2018

👍8 ❤1

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 on 16 Aug 2018

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

fejta-bot on 15 Sep 2018

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

fejta-bot on 19 Oct 2018

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.