Kind: Update docs.k8s.io/setup/learning-environment/minikube/

[mauilion]

What would you like to be documented:
We should update the docs on docs.k8s.io/setup/learning-environment/minikube/
to have a "kind" example.

Why is this needed:
kind may not yet be stable enough to provide for this but when it is we should document kind as a learning environment! With the capabilities around multinode I think it can be a more useful learning env than minikube in many ways.

[BenTheElder]

so minikube recently followed with minikube.sigs.k8s.io for docs, I think the plan going forward is to link out to upstream docs, we could probably link to our quick-start page once that is settled.

cc @zacharysarah

[BenTheElder]

I think all the docs like this are external now, is there anything else we should still do here?

[BenTheElder]

/help

[k8s-ci-robot]

@BenTheElder:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[tao12345666333]

:+1:

[zacharysarah]

@BenTheElder 👋

I think all the docs like this are external now, is there anything else we should still do here?

Is this still your plan? If so, LGTM:

I think the plan going forward is to link out to upstream docs, we could probably link [the title page of this issue] to our quick-start page once that is settled.

[BenTheElder]

I think this is a good plan 👍

On Thu, Oct 24, 2019, 00:10 Zach Corleissen [e-mail]
wrote:

@BenTheElder https://github.com/BenTheElder 👋

I think all the docs like this are external now, is there anything else we
should still do here?

Is this still your plan? If so, LGTM:

I think the plan going forward is to link out to upstream docs, we could
probably link [the title page of this issue]
http://docs.k8s.io/setup/learning-environment/minikube/ to our
quick-start page once that is settled.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-sigs/kind/issues/766?email_source=notifications&email_token=AAHADKZPK2KH2IA6ZQZHZK3QQFC7HA5CNFSM4ILFV7XKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECD6Z3Q#issuecomment-545778926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHADK6PCHCFUAACLJAW5Y3QQFC7HANCNFSM4ILFV7XA
.

[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

[BenTheElder]

/remove-lifecycle stale
D: nobody wants to take docs issues it seems .. guess I'll need to bump this up my own TODOs

[vanou]

Hi @BenTheElder ! If possible I'll try this.
/assign

[BenTheElder]

Sorry for missing this comment, I think this happened! https://kubernetes.io/docs/setup/#learning-environment

they may both be removed though if I skimmed that correctly.

[zacharysarah]

@BenTheElder

they may both be removed though if I skimmed that correctly.

Maybe not--we're weighing the boundaries of third-party content to "in-project" rather than "in-tree", which would allow KinD (among others) to stay in k/website docs, with the understanding that it's still important to avoid dual-sourced content.

This specific issue may require discussion before action, given https://github.com/kubernetes/website/issues/15969.