Overview:

This feature will introduce transparency and visibility into cluster update end-to-end. (Read more in the parent XCMSTRAT).

Current Gaps:

1. Managed OpenShift's advantage is cluster update orchestrated and monitored by RH SRE. Yet, under the Cluster, the OCM Console does not have a dedicated section for Cluster update. The Cluster update configuration is under oddly-named 'Settings' tab.
2. When the upgrade is requested, there's a lag for few minutes before the scheduled upgrade is displayed in the screen (refer to HAC-5092 linked). The user expectation is that the UI show the configured/requested cluster update immediately - perhaps with a status pending which changes to scheduled upon API response return. 
3. After the cluster update is scheduled, there is no granular tracking across milestones. Service Logs come informing terminal statuses or delays but there's no way to track where in the update process the requested upgrade is. 

Proposal:

1. A dedicated TAB with title Updates/Upgrades containing following 3 sub-sections:
   • Update Configuration : existing functionalities such as one-time or recurring update, node-drain, and target version
   • Update Monitoring: New progress bar that shows high level milestones of upgrades end to end.
   • Update History/Analytics: New section to provide KPIs and analytics around past cluster updates: From/to OCP version, Duration of updates, Active Node(s), Drain Period.