Feature: adding a Dev Container to Minikube

[star3am]

Feature: adding a Dev Container to Minikube, enabling us to launch Minikube in a Github Codespace or in a Dev Container locally

• Enables us to quickly get Minikube running in a Github Codespace
• Enables us to quickly get Minikube running locally using Dev Containers

Once the Codespace or Dev Container is launched, we can run minikube start - Let's open a new Terminal tab

Now let's run minikube start

Now we should have minikube up and running and we can run minikube and kubectl commads

We can even bring up the Minikube Kubernetes Dashboard by running minikube dashboard --url

and opening the Minikube Kubernetes Dashboard location on our Github Codespace

This is to my knowledge the fastest way to launch Minikube on the internet for Development / Demo purposes

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: star3am
Once this PR has been reviewed and has the lgtm label, please assign spowelljr for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[minikube-bot]

Can one of the admins verify this patch?

[k8s-ci-robot]

Hi @star3am. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.