OpenShift Virtualization 5 console now links virtual machines to the networks they use
Red Hat says the web console in OpenShift Virtualization 5 shows the relationships between virtual machines and networks directly, extending networking workflows first shipped in version 4.21. The change matters to teams running virtual machines on OpenShift who need to troubleshoot connectivity.
What to do now
Red Hat has described, in a blog post, a change to the OpenShift Virtualization 5 web console focused on virtual machine networking. The aim is to surface the relationship between a virtual machine and the networks it is attached to, without leaving the console pages administrators already use.
In practice, the console is meant to answer two questions that come up during an outage: which network a given virtual machine is on, and which virtual machines use a given network. That information appears as clickable links on existing pages rather than in a separate tool.
The features build on the workflows for creating and connecting VM networks that shipped with OpenShift Virtualization 4.21. Red Hat notes that the underlying model is still standard Kubernetes networking, so this is an interface improvement rather than a change to the network architecture.
The published excerpt does not state the general availability date of OpenShift Virtualization 5, the OpenShift version requirements, or which secondary network types the new views cover. Administrators should check the official release documentation for those details.
What to do now
- Check which OpenShift Virtualization version your clusters run and review the version 5 documentation for upgrade prerequisites.
- If you are still on a release older than 4.21, review the networking workflows introduced in that version, since the new views depend on them.
- After upgrading, add the console's VM-to-network views to your troubleshooting runbooks.