Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support kubernetes dashboard. #3

Closed
dlorenc opened this issue Apr 18, 2016 · 9 comments
Closed

Support kubernetes dashboard. #3

dlorenc opened this issue Apr 18, 2016 · 9 comments

Comments

@dlorenc
Copy link
Contributor

dlorenc commented Apr 18, 2016

No description provided.

@dharmit
Copy link

dharmit commented May 4, 2016

This can be achieved once you've configured the kubectl binary as mentioned here.

I downloaded the yaml file, uncommented line 50 to use appropriate IP-Port combination, and proxy it. It worked fine.

@dlorenc
Copy link
Contributor Author

dlorenc commented May 4, 2016

Thanks for trying this out!

@dlorenc
Copy link
Contributor Author

dlorenc commented May 6, 2016

Ref: kubernetes/kubernetes#23727

@dlorenc
Copy link
Contributor Author

dlorenc commented May 25, 2016

Update: I tried it and it doesn't work. We need to include the cluster internal IP (10.0.0.1) in the cert we generate. Sending a PR, then we can close this!

@vishh
Copy link
Contributor

vishh commented May 25, 2016

@dlorenc Can we run the dashboard by default?

@luxas
Copy link
Member

luxas commented May 25, 2016

Yes, we should have it by default, with a flag to disable

@dlorenc
Copy link
Contributor Author

dlorenc commented May 25, 2016

What's the best way to run this by default? Just create the pod/deployment directly from minikube or pass it as a flag to the APIServer at startup time somehow? Maybe as an addon?

@vishh
Copy link
Contributor

vishh commented May 25, 2016

Run it as an addon. Have minikube create the dashboard.

On Wed, May 25, 2016 at 11:26 AM, dlorenc notifications@github.com wrote:

What's the best way to run this by default? Just create the pod/deployment
directly from minikube or pass it as a flag to the APIServer at startup
time somehow? Maybe as an addon?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#3 (comment)

@dlorenc
Copy link
Contributor Author

dlorenc commented May 25, 2016

Looks like we first need to bootstrap the addon-manager, then we can enable this as an addon. I'll close this bug since we support it now, and open others to track the next work items.

@dlorenc dlorenc closed this as completed May 25, 2016
jimmidyson added a commit to jimmidyson/minikube that referenced this issue Jul 14, 2016
s-urbaniak pushed a commit to s-urbaniak/minikube that referenced this issue Oct 13, 2016
s-urbaniak pushed a commit to s-urbaniak/minikube that referenced this issue Oct 13, 2016
castlemilk pushed a commit to castlemilk/minikube that referenced this issue Jun 29, 2019
# This is the 1st commit message:

Fix doc comment version.gitCommitID doc


# This is the commit message kubernetes#2:

Add hyperkit doc


# This is the commit message kubernetes#3:

Add commit id to docker-machine-driver-kvm2 version


# This is the commit message kubernetes#4:

removed label selector for registry-proxy daemonset

# This is the commit message kubernetes#5:

Add support to custom qemu uri on kvm2 driver


# This is the commit message kubernetes#6:

Improve hyperkit vm stop


# This is the commit message kubernetes#7:

Make virtualbox DNS settings configurable 


# This is the commit message kubernetes#8:

added integration tests for registry addon
medyagh referenced this issue in medyagh/minikube Jul 30, 2019
# This is the 1st commit message:

organize integration tests files by type

# This is the commit message #2:

Adding separate profile for each kind of test

# This is the commit message #3:

Adding clean up to delete newly added TestVms

# This is the commit message #4:

goimport

# This is the commit message #5:

making them run in parallel
hendisantika added a commit to hendisantika/minikube that referenced this issue Apr 3, 2020
tstromberg pushed a commit that referenced this issue Apr 9, 2020
klaases pushed a commit to klaases/minikube that referenced this issue Apr 14, 2022
propagate GOOGLE_CLOUD_PROJECT env var to all known variants
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants