-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
5
-
False
-
True
-
The API for this feature has not been designed nor developed. SDE Jira for the work is unknown.
NOTE: The concept of maintenance schedules is out of scope
User story:
Because hosted (hypershift) ROSA clusters will always require a maintenance schedule, as a user, I want to enter a maintenance schedule for control planes only. This maintenance schedule may be individual (the user will choose the version in the future) or recurring where the user would enter a day/time for needed updating.
Acceptance criteria:
- Users must choose between individual (and choose the exact version at a later time after the cluster has been created) and recurring where the cluster will be automatically updated.
- For hosted (hypershift) control plane if the user chooses a recurring schedule, users are required to enter a day and time (in UTC) for a maintenance start time.
(if api is available)For hosted (hypershift) control plane, users are required to enter a day and time (in UTC) for a maintenance close time.- Data entered will be shown on the review page (both standalone and hosted ROSA wizards)
- The next button will not move the user to the next step if required information, including maintenance window day(s)/times(s) are not provided.
- [technical] Data is prepared to be sent to the api for the standalone wizard
Mockups:
Mockups |PD 1434
OLD Mockups:
------------------------------------------------------------------------------------------
Implementation details
Summary:
This is story is part of a set of changes for the cluster updates (HAC-2886, HAC-2887, HAC-2888).
Notes:
There are numerous text and formatting changes from the existing cluster updates component(s). An investigation will need to be done to determine if modifying the existing component should be done or if a new component just for Hypershfit should be created.
There is a new api endpoint to send update_policy for the control plane: /api/clusters_mgmt/v1/clusters/{cluster_id}/control_plane/upgrade_policies. This new endpoint should be used instead of the endpoint used for OSD/ROSA clusters.
API design doc - https://docs.google.com/document/d/17rgmcD6zX_jL28QnpHz3cPwYdE0wn7M9WpKau09JCfI/edit#
- depends on
-
HAC-2415 [Hypershift ROSA][MVP][Technical] Create a feature gate for Hypershift ROSA feature
- Closed
-
HAC-2416 [Hypershift ROSA][Wizard] Select control plane type (step 2)
- Closed
-
PD-1434 [ROSA] HyperShift Cluster Creation for ROSA (Part 2)
- Closed
- is depended on by
-
HAC-2411 [Hypershift ROSA][Wizard] Final review of Review and Submit
- Closed
- relates to
-
HAC-2525 [ROSA Wizard][OSD Wizard] Cluster updates - change from UTC to 12-hour local
- Closed
-
HAC-2887 [Hypershift ROSA Wizard] Cluster updates - separate maintenance schedules
- Closed
-
HAC-2888 [Hypershift ROSA Wizard][MVP] Cluster updates - change update strategy ordering
- Closed