Examine Minikube pages for dual-hosted content and content that should move to minikube docs site

[aimeeu]

This is a Feature Request

What would you like to be added
Examine minikube pages to determine what should be hosted by minikube docs and what should be hosted by k8s docs.

Following the discussion on dual-hosted content (#15576), I think guides for installing minikube should be in the minikube project's docs, and then the k8s docs link to those installation guides. State that the prerequisite for the Installing Kubernetes with Minikube page is successful installation of minikube and point to minkube docs.
Already the k8s docs are stale with regard to container runtimes that minikube supports.

k8s-specific how-to pages should remain in k8s docs.

Candidates to be removed from k8s docs and/or moved to minikube docs:

• Install Minikube this page is similar to https://minikube.sigs.k8s.io/docs/start/linux/
• Installing Kubernetes with Minikube
  • this whole page needs to be examined and reworked
  • minikube features section duplicates (and omits) content in https://minikube.sigs.k8s.io/docs/overview/
  • Starting a Cluster specifying the k8s version, specifying a VM driver, starting the cluster on alternate container runtimes, and use local images by re-using the Docker daemon sections are candidates to move to minikube docs (if not already there)
  • Add-ons section
  • Additional Links section
  • Community section
  • Hello Minikube references this page

Why is this needed
Dual-hosted content places undo burden on maintainers to ensure content is up-to-date in both places.

With all minikube installation configuration instructions on the minikube site, hopefully all minikube environment errors will be directed to the minikube team.

Comments
Relates to #15576 Clarify style guide: eliminate third-party content
Relates to #15748 Umbrella Issue: Remove Third-Party Content
Also see closed issue #6339 Restructure and Rewrite Minikube docs

[RA489]

/assign @RA489

[sftim]

/sig cluster-lifecycle

[sftim]

Will this work eventually mean filing docs issues against the Minikube repo?

[aimeeu]

It may - really depends on what @RA489 finds. In my quick review yesterday, I found duplicate content that was outdated in kubernetes/website when compared to the minikube website and docs. minikube has its own contributing to docs page!

[RA489]

I think as most of the doc has been to moved to minikube site we can remove the duplicate content.
@tstromberg wdyt?

[tstromberg]

YES!

@zacharysarah and I discussed this briefly when the new minikube docs site launched (two weeks ago), and I'm now convinced that we should replace the duplicate content from kubernetes/website with pointers to the minikube docs site. Make it so!

It slightly outside of the scope of this issue - but I am also open to moving additional minikube-related content from kubernetes/website to the minikube site. There are glaring omissions on both sides. That said, it may make sense for 'Hello Minikube', for example, to continue to exist on the Kubernetes website.

[aimeeu]

@tstromberg - thanks for your feedback! I agree that the Hello Minikube tutorial can stay since it is primarily about using Kubernetes. So probably the only content in Hello Minikube that needs to be updated are the Minikube links at the top of the page.
@RA489 thanks for working on this!

[tstromberg]

@RA489 - thanks for working on this. Anything I can help out with?

[dims]

/hold

please see the hold on the umbrella issue

[fejta-bot]

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

[tstromberg]

Are we able to move on this issue yet? I'd really like to begin dismantling the duplicate and outdated reference information on the Kubernetes website related to minikube - though keep the great "Hello Minikube" tutorial that isn't duplicated elsewhere.

[zacharysarah]

@dims 👋 Given that this issue is reasonably isolated from larger policy questions (i.e., this issue involves re-homing content specific to Minikube with the consent of its contributors), are you OK with lifting the hold?

[dims]

/hold cancel

[zacharysarah]

@dims Thanks! 🙏

@tstromberg Go for it!

[fejta-bot]

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

[zacharysarah]

/remove-lifecycle rotten

[tstromberg]

/assign

[fejta-bot]

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]

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]

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

[sftim]

/remove-lifecycle rotten
/triage accepted