Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-1025

Creating a node pol on a HCP cluster - Enforce maximum 60 node limit across a cluster

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • OCM UI Sprint 245, OCM UI Sprint 246

      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

              kdoberst Kim Doberstein
              kdoberst Kim Doberstein
              Vitor Graziano Vitor Graziano (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: