[minikube dashboard] Home page Read Dashboard Description Link has expired

[gdmrw]

What Happened?

404⬇️

https://kubernetes.io/docs/user-guide/ui/

Attach the log file

log.txt

Operating System

macOS (Default)

Driver

Docker

[afbjorklund]

This got broken here: kubernetes/website@b832ead

/docs/user-guide/ui/ /docs/tasks/access-application-cluster/web-ui-dashboard/ 301

https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/

But I don't think it is something in minikube, sounds like a problem for SIG UI or SIG docs?

[medyagh]

@panyam

[panyam]

hey @afbjorklund Sorry trying to find may way around this. The docs/user-guide/ui path doesnt seem to be referred anywhere. Do you mind sharing where this 404 link is actually used?

[afbjorklund]

I don't know, it wasn't reported... Just saw that it was removed after a couple of years, and now the redirect is dead

I think I saw it in some text on the legacy dashboard, so could look in that repo perhaps - but I don't think it was from minikube?

[panyam]

Ah thanks @afbjorklund. Ive created a PR for it in the dashboard repo:

kubernetes/dashboard#9851

[gdmrw]

Hello, Thanks for the discussion! I'm sorry for my vague description, but let me explain again.
This issue is found in my first installation and execute the minikube dashboard command.
When the workload is empty, there will be a sentence show that

There is nothing to display here
You can deploy a containerized application, select a different namespace, or read the Dashboard description to learn more.

And then I clicked the read Dashboard description the 404 page show up. You can check the below image

BTW, it is showed in Chinese version so the the problem may be in the translation version.

Best regards

[k8s-triage-robot]

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned