Cluster Manager

The OpenShift Cluster Manager (OCM) is a SaaS product that gives OpenShift 4 customers a view of all of existing clusters regardless whether they are on-premises or in the public cloud. It also serves as the launching point for creating new clusters. I serve as the primary designer for this product and work very closely with both PM and engineering.

Cluster views

Customers entering the application land on a list of their clusters which provides information about the clusters’ health, subscription status, software version, as well as infrastructure provider and region. Because OCM exists alongside other SaaS products, I have worked with designers across teams on a consistent approach to filtering, the placement of actions and pagination, etc.

Mockup of cluster list view

Users can drill down from the list of clusters to a details page for their cluster. Within the cluster details view there are two (or sometimes three, as in the screenshot below) tabs that allow users to see different facets of the cluster. The Overview tab gives users a snapshot of resource usage, while the details section is essentially a set of facts about the cluster. This format is used on resource detail pages throughout the web console of OpenShift itself, and should be familiar to those users.

Screenshot of cluster list view

The other details view that’s common across all cluster details pages is the Monitoring tab. This purpose of this tab is to give a high-level sense of the cluster’s health. We took some inspiration in terms of the page design from status pages. We opted for this approach rather than something more resembling a dashboard for several reasons. The web console for the cluster itself has a dashboard, which we are not able to duplicate here because we have neither the same amount of data, nor the same sampling rate. The idea is then to show users any critical problems and send them to the cluster itself to act on those problems.

Mockup of cluster details monitoring tab

Actions and flows

Within the different views there are actions users can take on their clusters to affect the cluster’s subscription status, change whether or not the clusters will show up in the list, and to create managed clusters. Below are some designs for several of the flows.

Mockup illustrating archival flow

Detail from the flow for creating a managed cluster

Detail from designs for adding the web console URL for a cluster