Skip to content

Commit ace060b

Browse files
authored
Update KubeVirt node placement explanation
Linter fixes.
1 parent 5b89e57 commit ace060b

File tree

1 file changed

+0
-1
lines changed
  • website/blog/2026-01-30-kubevirt-on-aks

1 file changed

+0
-1
lines changed

website/blog/2026-01-30-kubevirt-on-aks/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,6 @@ Using the [Standard_D4s_v5](https://learn.microsoft.com/azure/virtual-machines/s
7070

7171
Notice the empty `nodePlacement: {}` line. By default, KubeVirt sets the node-affinity of control-plane components to control-plane nodes. Because AKS control-plane nodes are fully managed by Azure and inaccessible to KubeVirt, this update to nodePlacement avoids potential failures.
7272

73-
7473
### Confirm the KubeVirt pods are up and running on the cluster
7574

7675
Once all the components are installed, you can quickly check if all the KubeVirt components are up and running properly in your cluster:

0 commit comments

Comments
 (0)