Is your feature request related to a problem? Please describe.
The SaaS dashboard has dedicated Machines and Clusters pages, full pages with cards, status, limits, and a connect flow. The OSS dashboard's sidebar instead crams machines and clusters into inline collapsible list sections (see sidebar in a fresh local install), no dedicated page, no card view, nothing beyond a name + status dot per entry.
This is presumably fine when OSS usage is "one machine, maybe a couple of clusters," but it's a real UX inconsistency between the two products and gets cramped fast once someone connects a handful of machines/clusters via + Add machine/multiple kubeconfigs.
Describe the solution you'd like
Bring OSS closer to SaaS's Machines/Clusters page pattern: dedicated routes/pages with a proper card grid, matching what's already built and working in the SaaS frontend (frontend/app/(main)/machines and frontend/app/(main)/clusters in the SaaS repo can likely be adapted, the two frontends share a lot of component structure already).
Additional context
Not urgent for typical single-machine OSS usage, but worth doing before OSS usage patterns grow past a handful of connected machines/clusters.
Is your feature request related to a problem? Please describe.
The SaaS dashboard has dedicated
MachinesandClusterspages, full pages with cards, status, limits, and a connect flow. The OSS dashboard's sidebar instead crams machines and clusters into inline collapsible list sections (see sidebar in a fresh local install), no dedicated page, no card view, nothing beyond a name + status dot per entry.This is presumably fine when OSS usage is "one machine, maybe a couple of clusters," but it's a real UX inconsistency between the two products and gets cramped fast once someone connects a handful of machines/clusters via
+ Add machine/multiple kubeconfigs.Describe the solution you'd like
Bring OSS closer to SaaS's Machines/Clusters page pattern: dedicated routes/pages with a proper card grid, matching what's already built and working in the SaaS frontend (
frontend/app/(main)/machinesandfrontend/app/(main)/clustersin the SaaS repo can likely be adapted, the two frontends share a lot of component structure already).Additional context
Not urgent for typical single-machine OSS usage, but worth doing before OSS usage patterns grow past a handful of connected machines/clusters.