Closed xphyr closed 3 years ago
Hi @xphyr. Thanks for your PR.
I'm waiting for a kubevirt 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.
/ok-to-test
I picked an arbitrary date for the publication out a week.... let me know if I need to change anything there as I wasnt sure when it might get published.
@xphyr Publishing date is arbitrary. It's up to you.
I have migrated the setup/demo over to a Fedora 32 setup. I am also using the process you suggested for deploying minikube. I am re-running the entire set of steps from the top to ensure that they work properly and I captured all the changes. This should be more straight forward for someone to follow.
I helped you out with a few tweaks to help CI along.
We are clear for take off!
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mazzystr
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This PR is in response to Issue #711 The blog post details how to use the new Intel vGPU detection added in kubevirt release v0.40.0. The idea is to show how to try this feature out on a single machine leveraging Centos 8.3 and minikube. It is a semi-complex topic because it really combines multiple existing blog posts such as:
I have tried to pull all this together in one post. Please let me know what thoughts and feedback you have on this, and thanks for your consideration.