docs: Mixed signals regarding `minikube dashboard`

[adesso-os]

https://minikube.sigs.k8s.io/docs/drivers/none/ first says:

• Many minikube commands are not supported, such as: dashboard, mount, ssh

Then it says:

• minikube with the none driver has a confusing permissions model, as some commands need to be run as root ("start"), and others by a regular user ("dashboard")

If minikube dashboard is not supported, why mention it in the next line?

[afbjorklund]

The documentation is outdated, the none driver does not need to run as root anymore (it uses sudo)

Patches to docs welcome

EDIT: missed "not", oops

[adesso-os]

That didn't really clarify the subject for me. How is using sudo different from running as root? I also assume you're missing a "not" in your statement maybe?

[afbjorklund]

Instead of running the minikube program as root and reading config from /root, it runs as your regular user and then adds a "sudo" to the system commands that actually need it

[klaases]

Hi @adesso-os, did you want to create a PR to update the doc?

Else, I could create a PR if you don't mind, could you let me know the specific change you are seeking?

[adesso-os]

@klaases I sadly still haven't understood the difference. I left the issue open in case someone else can handle it. So, please do :)

To clarify, the quoted paragraphs seem to contain contradicting information. It first says the dashboard command is not supported, then it mentions the dashboard command needs to be run as a regular user. If it isn't obvious how that can be confusing, then I'd rather not invest any more time into this.

[medyagh]

@adesso-os I thin the difference @afbjorklund pointed out that minikbue no longer needs Root for none driver, but only sudo (still using same user but as super user)

[adesso-os]

@medyagh Yeah, but I wasn't able to project what that means onto the section of the documentation. If it's clear to you guys, please just make the change or close the ticket if it's invalid. I don't even use minikube.

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

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.