Problem statement:

New users, especially those migrating from VMware, face a steep learning curve when working with OpenShift and Kubernetes networking. The use of Kubernetes-native terminology without explanation, lack of real-time guidance, and the absence of implied and connected workflows contribute to user frustration and misconfiguration. These challenges impede onboarding, increase support burden, and negatively affect perception of the platform's usability.

Background / context:

VMware administrators are accustomed to simplified networking models with guided UI workflows. OpenShift Virtualization exposes lower-level Kubernetes concepts (e.g., NetworkAttachmentDefinition, bridge mappings, bonding), often requiring YAML editing and an understanding of cluster networking internals. Without contextual help or guided experiences, users find the platform difficult to adopt.

Multiple research inputs (doc) show that terminology confusion and lack of UI hints are persistent blockers to task completion. This issue is compounded by the complexity of also learning storage, compute, and RBAC models concurrently.

Proposed strategy and UXD recommendation:

• Inline terminology tooltips and definitions: Provide non-intrusive explanations of key networking terms (e.g., NAD, bridge, bonding) via hoverable tooltips, glossary popovers, and links to documentation.
• Contextual real-time hints: Implement real-time UI hints when configuration conditions are not met (e.g., show “This NAD won’t work without a bridge mapping” immediately when the bridge is missing).
• Guided configuration flows: Add step-by-step guidance or "smart defaults" when creating networking resources to prevent user error and reduce cognitive burden.
• Progressive disclosure: Hide advanced fields by default, only surfacing them when relevant to the user’s context, making the form experience less overwhelming.
• Enhanced empty states / start screens: Use the entry point of the networking section to orient new users with diagrams or short walkthroughs.

Value / outcome:

• Reduces user frustration and support tickets caused by incorrect configurations

• Increases successful onboarding of VMware users

• Enhances user trust and confidence in the platform

• Builds a more intuitive and guided experience in line with expectations set by other virtualization platforms

Priority recommendation:

High — Addresses core onboarding friction and supports BU-level goals to grow adoption by non-Kubernetes-native users.