Proposed title of this feature request:

ROSA Clusters Update Dependencies

What is the nature and description of the request?:

Customers often run multiple clusters on ROSA for different stages of their environment, for example for non-production and production workloads. Customers test changes and different configurations on their non-production clusters first before applying them to the typically more critical production clusters.

This request asks for a feature in the Cluster Manager to be able to define update dependencies between clusters. Customers should be able to define an update dependency between clusters to make sure non-production clusters are updated before production clusters are updated.

Ideally, a customer should be able to configure that a cluster updates to a new version of OpenShift only if another specific cluster has been running that version for at least n days. A simple dependency (cluster A needs to be the same or higher version before updating) could be another implementation possibility.

Why does the customer need this? (List the business requirements here):

At the moment, customers specify different week days for their cluster updates, for example updating non-production clusters on a Tuesday and then later in the week on Thursday updating production clusters to that same version.

Having a fixed dependency would help avoid the issue that the production cluster is updated to a version that has not been tested on a non-production cluster. This improves stability of the customer workloads and gives customers greater confidence for cluster updates.

List any affected packages or components:

Cluster Manager
ROSA Update system

Cloned from https://issues.redhat.com/browse/OHSS-27786