User story:

Because hosted (hypershift) ROSA clusters will always have a recurring update strategy, as a user, I don't want the option to choose "individual" update strategy. 

Acceptance criteria:

• For hosted (hypershift) control plane, there isn't an option to choose between individual and recurring updates. The cluster will be updated automatically (aka recurring)
• Once created, the cluster will automatically start to be upgraded to the next path (z-stream) version after the "start time" on the day of the week chosen by the user.
• There is more detailed text specifically for hosted (hypershift) control plane around update schedule
• Data entered will be shown on the review page (both standalone and hosted ROSA wizards)
• [technical] Data is prepared to be sent to the api for the standalone wizard

Mockups:

Mockups

PD 1434

------------------------------------------------------------------------------------------

Implementation details

Summary:

There is no concept of “manual” or “individual updates” for hosted (hypershift) control planes – all patch (aka z-level) upgrades will be done automatically

Major tasks:

• If using an existing component, hide the individual vs recurring updates option and automatically set it to “recurring”
• Use new next just for hosted clusters

Notes:

• The design and microcopy have not been finalized yet
• This has an impact on day 2 operations inside the cluster settings tab.  For example, can a user switch to "individual updates" after the cluster has been created?

More research needed: