Problem with "Deploy and Access the Kubernetes Dashboard"

kubernetes / website

Kubernetes website and documentation repo:

https://kubernetes.io

Creative Commons Attribution 4.0 International

4.54k stars 14.48k forks source link

Problem with "Deploy and Access the Kubernetes Dashboard" #46475

Open janmg opened 6 months ago

janmg commented 6 months ago

The kubernetes dashboard documentation now with v7 using helm, states to use port-forward to the kong proxy for helm deployments and to access the dashboard on https://localhost:8443/. the kubectl proxy doesn't work because the helm deployment doesn't seem to deploy an endpoint and the http request results in an error

no endpoints available for service \"kubernetes-dashboard\"

So instead of proxy the documentation tells to use port-forward https://github.com/kubernetes/dashboard/tree/master/docs/user/accessing-dashboard

kubectl -n kubernetes-dashboard port-forward svc/kubernetes-dashboard-kong-proxy 8443:443
Now access Dashboard at: https://localhost:8443/

k8s-ci-robot commented 6 months ago

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

thisisharrsh commented 6 months ago

/language en /sig docs

sftim commented 6 months ago

/retitle Problem with "Deploy and Access the Kubernetes Dashboard"

sftim commented 6 months ago

/kind bug

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

vaibhav2107 commented 2 months ago

/remove-lifecycle stale As PR is still open