MKE Virtualization (KubeVirt) section #101
Conversation
KoryKessel-Mirantis
changed the title
|
@KoryKessel-Mirantis - who is the approver now? Why can't I approve? |
Try that again, I've updated your permissions |
| --- | ||
|
|
||
| Virtualization functionality is available for MKE through [KubeVirt](https://kubevirt.io/), a Kubernetes extension with which you can natively run | ||
| Virtual Machine (VM) workloads alongside container workloads in Kubernetes |
|
|
||
| Virtualization functionality is available for MKE through [KubeVirt](https://kubevirt.io/), a Kubernetes extension with which you can natively run | ||
| Virtual Machine (VM) workloads alongside container workloads in Kubernetes | ||
| clusters. |
There was a problem hiding this comment.
I understand that it works this way as well, but let's keep the sources nice and well-formatted. Move the word "clusters" to the previous line, there is enough space there.
| weight: 3 | ||
| --- | ||
|
|
||
| Although it is not required to run KubeVirt, the virtctl CLI provides an |
There was a problem hiding this comment.
mark "virtctl" as a command/tool
| https://binary.mirantis.com/?prefix=kubevirt/bin/artifacts. | ||
|
|
||
| 2. Run the following command, inserting the correct values for your | ||
| architecture and platform. For **ARCH** the valid values are |
There was a problem hiding this comment.
use backticks to format the inline text as code
There was a problem hiding this comment.
check throughout the commit
| wget https://binary-mirantis-com.s3.amazonaws.com/kubevirt/bin/artifacts/virtctl-1.3.1-20240911005512-darwin-arm64 -O virtctl | ||
| ``` | ||
|
|
||
| 3. Move virtctl to one of the :guilabel:`PATH` directories. |
There was a problem hiding this comment.
guilabel is not working in md
There was a problem hiding this comment.
That is most certainly correct!
Fixed.
| --- | ||
|
|
||
| The example scenario illustrated herein pertains to the deployment of a CirrOS | ||
| virtual machine. The scenario consists of three primary steps: |
There was a problem hiding this comment.
Remove the exact number of steps from "The scenario consists of three primary steps:"
This way the content is easier to maintain
There was a problem hiding this comment.
Edited to read:
"The example scenario illustrated herein pertains to the deployment of a CirrOS virtual machine, which is comprised by the following primary steps:"
| storage: 3Gi | ||
| ``` | ||
|
|
||
| 2. Run the following command to create the `PersistentVolumeClaim` resource |
There was a problem hiding this comment.
Create the PersistentVolumeClaim resource that you defined in the example-pvc.yaml file:
| pvc-claim-1 Bound pvc-b7d68902-f340-4b7e-8a36-495d170b7193 10Gi RWO hpp-local 10s | ||
| ``` | ||
|
|
||
| 4. Run the following command to attach the disk to your VM: |
There was a problem hiding this comment.
- Attach the disk to your virtual machine:
| {"bus": "virtio"},"name": "example-pvc"}}]' | ||
| ``` | ||
|
|
||
| 5. Restart the VM and access the console: |
There was a problem hiding this comment.
VM - virtual machine
you use it differently through the content, be consitent
There was a problem hiding this comment.
As the audience flips so easily between "virtual machine" and "VM" I made a conscious choice to do the same. Still, I know you are correct...even if you do have trouble spelling 'consistent'. :-)
Done.
| kubectl apply -f bridge-test.yaml | ||
| ``` | ||
|
|
||
| 3. Run the following command to attach the network interface to your virtual |
There was a problem hiding this comment.
- Attach the network interface to your virtual machine:
KoryKessel-Mirantis
deleted the
port-mke-virtualization-kubevirt-content-from-mke3715
branch
No description provided.