Add KIND as the options for spinning up a test kubernetes environment for the "Tasks" section examples

[opowbow]

This is a Feature Request

What would you like to be added
Under the Tasks sections, could we add KIND to the ways of setting up a kubernetes cluster ? Currently the section called : Before you begin, instructs the user as follows: " You need to have a k8s cluster " and it references minikube; then katacoda and https://labs.play-with-k8s.com

Why is this needed

KIND is another sound option for spinning up a kubernetes environment for the purpose of running through these task items

Comments
I am keen to work on this. Referencing @munnerz as I spoke to him about this before raising this issue

[sftim]

Thanks for the suggestion @opowbow
/kind feature
/language en

[Rajakavitha1]

Thanks for taking on this @opowbow!!! It would be great if you could add the content for KIND here: https://kubernetes.io/docs/setup/learning-environment/

[opowbow]

No problem. So this is creating the content for KIND so that it can be referenced throughout the website...? mainly from the "Tasks" sections...?

[Rajakavitha1]

No problem. So this is creating the content for KIND so that it can be referenced throughout the website...? mainly from the "Tasks" sections...?

It was more in terms of Getting Started with Kubernetes with KIND. Just like the one we now have for Getting Started for Kubernetes with Minkube: https://kubernetes.io/docs/setup/learning-environment/minikube/

Yes, we could have the install instructions for KIND under "Tasks" sections similar to the one we now have for Minikube.

[opowbow]

Yes sure. As I say , this content then is referenced in the task section. OK great . thanks

[Rajakavitha1]

Yes sure. As I say , this content then is referenced in the task section. OK great . thanks

Yes, works either ways :)

[zacharysarah]

I like making this information available to folks. I'd rather see us add a link to this information in KinD source rather than dual-source this info in k/website.

[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

[sftim]

/remove-lifecycle stale
/priority important-longterm