Cluster card anatomy

Each card should be a reusable Storybook component with these slots:

1. Connection type label — NON-VPS · AUTHENTIK or VPS · NETBIRD. 2. Cluster name — the user-provided display name, prominent and short. 3. Endpoint context — private address, hostname, or protected endpoint; truncate visually but expose the full value to assistive technology. 4. Status badge — AVAILABLE, CHECKING, OFFLINE, or REAUTH REQUIRED. 5. Rancher state — Rancher available, No Rancher detected, or Management cluster setup required. 6. Primary action — Launch. 7. Secondary action — Manage, for connection details and future maintenance actions.

The first version should keep the action model intentionally small:

  • Launch attempts to open the correct Rancher or protected endpoint;
  • Manage can initially open a connection-details view;
  • no dense telemetry, charts, or infrastructure graphics are required.