Uploaded image for project: 'OpenShift UX Product Design'
  1. OpenShift UX Product Design
  2. PD-929

Finalize cluster context switcher design


    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • Admin
    • None
    • OpenShift UXD Sprint 202, Console UXD Sprint 203, Console UXD Sprint 206, UXD Sprint 207, UXD Sprint 208

      Refine the visual styling of the dropdown and the various states, aligning more closely with the upcoming Project switcher design.

      Finalize the behavior of the Create Cluster button when ACM is and isn’t installed - do we point folks to OCM to create clusters instead? Do we duplicate OCM's Create page in-Console? Should OCM be hub-aware and point users to the ACM hub that manages that cluster to create a new one in the same family? Do we want to highlight that the ACM operator provides the ability to switch within the dropdown?

      Consider how to handle clusters that are visible to ACM but may be in weird states like installing, hibernated, etc. which wouldn’t show any useful information within the single-cluster Admin/Dev perspectives. Maybe a unique empty state could be shown if a cluster enters one of those states while the user is in its context.

      Dropdown states:

      • New clusters
        • ACM is not installed anywhere; install it to enable switching
      • Spoke clusters
        • ACM is available at the hub; go to that UI to switch clusters easily
      • Hub clusters
        • Switch clusters easily just like you can with Projects



      • (Slack) Mention of the ability to "favorite" clusters and access them quickly from ACM (and maybe launch a separate Console to more easily compare resources side-by-side, until/unless we devise something better)

            mceledon-1 Michael Celedonia (Inactive)
            abrarenrh Andy Braren
            0 Vote for this issue
            2 Start watching this issue