Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/How red hat openshift console connects virtual machines to the networks they use
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

How Red Hat OpenShift console connects virtual machines to the networks they use

Source: Red Hat•November 16, 2026 at 06:01 PM

How Red Hat OpenShift console connects virtual machines to the networks they use

In Red Hat OpenShift Virtualization 4.21, we shipped networking workflows that simplify how you create and connect virtual machine (VM) networks. In OpenShift Virtualization 5, the web console builds on those workflows—the same Kubernetes networking model, with clickable paths on pages you…

In Red Hat OpenShift Virtualization 4.21, we shipped networking workflows that simplify how you create and connect virtual machine (VM) networks. In OpenShift Virtualization 5, the web console builds on those workflows—the same Kubernetes networking model, with clickable paths on pages you already use.

Which network is this VM on? Which VMs use this network? These new features answer those questions on the pages you already live in when something breaks at 2 AM.

Building on the OpenShift Virtualization 4.21 foundation

This post builds on the VM networking workflows introduced in OpenShift Virtualization 4.21: Removing complexity from your virtual machine networking workflow. If you haven’t read that post yet, start there. In OpenShift Virtualization 4.21, we simplified how secondary networks attach to VMs. OpenShift Virtualization 5 brings those connections directly into the web console, allowing you to inspect network paths without switching tools.

The console features described in this article build on that foundation, so you can follow connections after you attach networks instead of reconstructing them. These updates are only available in OpenShift Virtualization 5 and later.

The new console features follow the same Kubernetes networking model as OpenShift Virtualization 4.21:

Traffic flows from your VM through a network definition layer, such as a NetworkAttachmentDefinition (NAD), UserDefinedNetwork (UDN), or ClusterUserDefinedNetwork (CUDN), before crossing a virtual bridge to the physical network interface card.

Figure 1: Architecture diagram showing the path from a VM or Pod through network definitions and a virtual bridge to the physical Network Interface Card (NIC).

What’s new in the console

In earlier releases, finding secondary networks required jumping across multiple resource pages, while setting up a service required writing manual YAML. The OpenShift Virtualization 5 web console adds:

  • Links from VMs to networks: On a VM's Configuration → Network tab, click a secondary network name to open its NAD, UDN, or CUDN details page.
  • Attached workloads view: On any NAD, UDN, or CUDN details page, open the Virtual Machines tab to see which workloads use that network.
  • Service creation form: Create a service with a form and a YAML view side by side.
  • Backend health in list views: The Services and Routes pages show backend health, so you can scan status without opening each item.

These build on the OpenShift Virtualization 4.21 attach workflows. Same networking model, more ways to follow the connections afterward.

From the network: Which VMs use this network?

Navigation now works in both directions: from a VM to its networks, and from a network to its VMs.

From the network: NAD, UDN, and CUDN details pages include a Virtual Machines tab, which works like the Pods tab on a service. A count badge on the tab shows how many VMs use the network. Within the tab, a table lists each VM's name, namespace, status, and interface. From this tab, you can customize table columns or attach and detach VMs directly. The console removes the VM's interface for this network but doesn't delete the VM.

Figure 2: The Virtual Machines tab on a NetworkAttachmentDefinition details page.

From the VM: On a VM’s details page, secondary network names are links on the Configuration → Network tab, and in the interfaces list on the Overview tab. Click a name to open its NAD, UDN, or CUDN details page. If someone deleted the network, the name displays as a broken link with a tooltip, not a 404 page.

Figure 3: VM Configuration → Network tab with a clickable secondary network name.

Create a service in Form view or YAML view

On the Networking → Services → Create Service page, you can configure a service in Form view or YAML view. Use the form view for guided fields: Service type, ports, and a pod selector that shows which pods match. Switch to YAML view when you'd rather edit the manifest yourself or need an API field that the form doesn't include.

Figure 4: Create Service page in Form view.

Scan Service and Route health from the list

The Services and Routes list pages now include a Health column. For each item, the column shows a status icon and the number of ready endpoints out of the total (for example, 2/3), so you can check readiness at a glance.

Status

Meaning

Healthy

All endpoints are ready

Degraded

Some endpoints aren’t ready or are failing

Down

No endpoints are ready

Unknown

Still loading health data

Figure 5: Services details page

Figure 6. Services page displaying health status and configuration details for active services.

Figure 7. Routes page displaying health status, locations, and service mappings for active routes.

A real troubleshooting scenario

Let’s say an app running on a VM stops responding through its service. Instead of running oc get endpoints and reading YAML, you can trace the problem in the console:

  • Go to Networking → Services and check the Health column for the service. Degraded or Down means some or all of the service's endpoints aren't ready, so the problem is on the backend side.
  • Open the service and check its pod selector. If the service shows Down with no endpoints, the selector might not match the VM's labels.
  • Fix the selector on the service's YAML tab.

Or say 2 VMs on the same secondary network can't reach each other:

  • Open one VM's Configuration → Network tab and click the secondary network name to open its NAD, UDN, or CUDN details page.
  • On the network's Virtualization tab, check whether the other VM is in the list. If it’s not, click Add virtual machines to attach it.

Next steps

By bringing network visibility into the console pages you rely on daily, OpenShift Virtualization removes mental friction so you can diagnose and resolve cluster issues faster. To use these console features, upgrade your cluster to OpenShift Virtualization 5 or later.

Ready to simplify your VM networking? Try these console workflows in the Red Hat OpenShift Developer Sandbox, or read the official Red Hat OpenShift networking documentation to configure your first network attachment.

← All articles

What this article says

More in Software Development

All →
5 Ways to Get the Most Out of AI at Your Hotel
Stayntouch

5 Ways to Get the Most Out of AI at Your Hotel

8 Sales Promotion Types to Boost Holiday Revenue [2026]
Lightspeed

8 Sales Promotion Types to Boost Holiday Revenue [2026]

Freshworks alums raise $53M to take on Salesforce, HubSpot with AI-native CRMПресса
Salesforce

Freshworks alums raise $53M to take on Salesforce, HubSpot with AI-native CRM

Fern is now Postman’s home for API Dev Portals
Postman

Fern is now Postman’s home for API Dev Portals

Unlocking mission-critical innovation: Microsoft Azure Red Hat OpenShift IL5 is Now Available on JWCC
Red Hat

Unlocking mission-critical innovation: Microsoft Azure Red Hat OpenShift IL5 is Now Available on JWCC

Guest Advocacy in Hospitality: How to Turn Happy Guests into Brand Ambassadors
Rms Cloud

Guest Advocacy in Hospitality: How to Turn Happy Guests into Brand Ambassadors

More from Red Hat

Unlocking mission-critical innovation: Microsoft Azure Red Hat OpenShift IL5 is Now Available on JWCC
Red Hat

Unlocking mission-critical innovation: Microsoft Azure Red Hat OpenShift IL5 is Now Available on JWCC

Friday Five — November 13, 2026
Red Hat

Friday Five — November 13, 2026

Now in Developer Preview: The self-managed Red Hat Enterprise Linux command-line assistant
Red Hat

Now in Developer Preview: The self-managed Red Hat Enterprise Linux command-line assistant

Your move to Red Hat OpenShift Virtualization doesn't have to wait on VDDK
Red Hat

Your move to Red Hat OpenShift Virtualization doesn't have to wait on VDDK

Why Lightwell pairs dependency backports with upstream collaboration
Red Hat

Why Lightwell pairs dependency backports with upstream collaboration

5-minute demo: How to manage applications at scale with Red Hat OpenShift
Red Hat

5-minute demo: How to manage applications at scale with Red Hat OpenShift