Normal Feature Overview
This feature introduces an improved node-centric view within OpenShift to support users managing virtual machines (VMs) and bare metal workloads. It aims to simplify node status comprehension, especially around storage and networking, for non-Kubernetes-expert users. The feature enhances visibility into the underlying infrastructure—including VMs, storage, networks, policies, configurations, and event timelines—enabling users to confidently manage critical workloads.
Detailed internal Jira Tracking for this effort
https://issues.redhat.com/browse/HPUX-883
Design document
https://docs.google.com/presentation/d/1VCThFMMttP5XWpFY32AHDD7uF-CsXmm2u6FeVvEtL1Y/
Goals
To enable non-Kubernetes-native users (especially those using click-ops workflows) to effectively manage and troubleshoot nodes, particularly in Virt and Bare Metal scenarios where nodes are not disposable. The goal is to provide a clear, integrated view of node health, status, and associated storage and network configurations, thereby reducing operational friction and risk.
- Who benefits?
Virt administrators and operators responsible for running and maintaining critical virtualized or bare metal workloads.
- What's the difference?
Today: Users struggle to understand node health, connectivity, and storage information due to scattered or missing data across OpenShift components.
With this Feature: Users have an integrated view of node-related resources, including VMs, PVCs, storage classes, logs, events, and health data—all accessible from a unified UI.
Requirements
| Requirement | Notes | isMvp? |
|---|---|---|
| Provide unified node-level view of associated VMs, Machinesets, MCP, storage, and networks | To include VM inventory per node, storage accessibility, network configuration | Yes |
| Show capacity and health status of both physical storage and PVCs and their underlying storage systems | Supports proactive resource management and troubleshooting | Yes |
| Indicate storage mapping from host > node > PVC > VM | Provides end-to-end visibility into storage flow | Yes |
| Provide unified node-level view of associated performance | To include VM performance per node | Yes |
Out of Scope
- Full end-to-end observability tooling for storage systems (e.g., integrating third-party storage monitoring platforms)
- Deep storage class configuration editing in the UI
- Automatic remediation of node-level issues
Background, and strategic fit
Today’s OpenShift UI does not meet the expectations of VMware customers, non-Kubernetes-native users managing critical infrastructure. In Virt workloads, nodes are persistent and crucial to service availability—unlike traditional Kube environments where nodes are ephemeral. Improving the node-centric experience is aligned with Red Hat’s strategic focus on user experience, platform reliability, and enterprise-grade virtualization.
Assumptions
- Target users are less familiar with Kubernetes internals.
- VMware users prefer a GUI-driven approach (click-ops) over CLI or YAML editing.
- Storage and networking are top priorities for troubleshooting.
- Logs and events tied to nodes are critical to operational insight.
Customer Considerations
- Need for clear, actionable insights without requiring Kubernetes expertise.
- Desire for consistency and simplicity across the UI for storage/network observability.
- Customers expect performance efficiency—no noticeable impact to cluster due to this UI feature.
Documentation Considerations
- Documentation should include screenshots and descriptions of the new node view interface.
- Provide a mapping guide to help users understand relationships between nodes, VMs, PVCs, and storage systems.
User Experience Considerations
- Deck linked above
- UI should highlight relationships between node(server) → VM → physical resources.
- UX should account for both cluster-wide administrators and VMware customers.
- Collaboration with UXD (via Andrew Sullivan) to finalize mockups and user flows is in progress.