-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
User story:
So that I don't accidentally try to add more than the maximum number of nodes (51) across an HCP cluster, as a user, I want the UI to not give options that would cause the cluster to go over the maximum number of nodes when adding a new machine pool.
Acceptance criteria:
- When adding a HCP machine pool (aka node pool):
- For non-autoscaling, the drop-down options do not let me go over 51 total nodes. For example: if the cluster has three nodes: mp-A has 3 nodes, mp-B has 2 nodes, and mp-C has 10 nodes. If I edit mp-C, the largest option would be 46 nodes.
- For autoscaling, I cannot push the + button on the max nodes to go over 51 total nodes.
- For autoscaling, if I enter a value in the max nodes that would go over 51 total nodes, an error is shown
Mockups:
No design changes, just a limit on the max number of nodes to 51
- is blocked by
-
OCMUI-1156 [ROSA Hypershift] No validation in place for Maximum nodes count when it exceeds the allowed limits from "Add machine pool"
- Closed
- links to
- mentioned on