Update hyperkit to note deprecation, note Apple Silicon hypervisor alternatives

[vielmetti]

Point at the current hypervisor options for Apple Silicon with a warning message at the top of the hyperkit driver page.

fixes #23005

Even if the feature is deprecated the codebase is still there for it; there are other open issues targeting removal of this code. First step is to correctly set expectations for lack of support.

Preview: https://deploy-preview-23027--kubernetes-sigs-minikube.netlify.app/docs/drivers/hyperkit/

[k8s-ci-robot]

Welcome @vielmetti!

It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/minikube has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @vielmetti. 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.

Details

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.

[minikube-bot]

Can one of the admins verify this patch?

[nirs]

@vielmetti Thanks, this looks like a good minimal change before we remove the driver.

[vielmetti]

updated as requested, I think I got the ref syntax right

[nirs]

@vielmetti You got the link syntax right - you can see the preview:
https://deploy-preview-23027--kubernetes-sigs-minikube.netlify.app/docs/drivers/hyperkit/

However GitHub alerts are not supported in the docs - the pages are not rendered by GitHub. We have another syntax for warnings - you can find it in other docs.

Example warning:

{{% alert title="Warning" color="warning" %}}
Warning text...
{{% /alert %}}

I think the warning should be first on the page - before the overview.

[nirs]

Thanks

[vielmetti]

@prezha I think this is ready for your review - take a look at https://deploy-preview-23027--kubernetes-sigs-minikube.netlify.app/docs/drivers/hyperkit/ for the preview

[nirs]

Nobody had any concern in the last 3 days.

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nirs, vielmetti

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [nirs]

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

[nirs]

Testing is not require for docs only change but the workflows are not configured correctly.

/ok-to-test

[k8s-ci-robot]

@vielmetti: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-minikube-docker-crio-linux-x86	d6f2133	link	false	/test pull-minikube-docker-crio-linux-x86

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.