-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
-
False
-
XCMSTRAT-371 - HCP: Guest clusters supporting up to 500 worker nodes
-
(10/7) All related MRs merged and promoted
-
-
-
OCMUI Core Sprint 259, OCMUI Core Sprint 260
ROSA HCP has moved the default max to 250.
But depending of the organization, there are exceptions (some customer are open to create clusters up to 500).
But depending on the ocp version, the max size should be back to 90.
Then when customer tries to create a cluster beyond limits in day 1, or modify an existing one in day 2; it will get a 400 error i.e. cluster beyond limit.
Then UI should also align with this.
Requirements:
- The default max nodes value should be changed from 51 to 250.
- Orgs with exception should have max value 500
The exception is by feature flag "max-compute-nodes-500".
- Clusters with insufficient OCP version should have max value 90.
Minimal versions to allow more then 90 nodes: 4.15.15, 4.14.28.
Open questions:
How can UI tell which org can scale up to 500?Which OCP versions supports scaling up to 90 nodes only?
- duplicates
-
-
- Closed
-
- is related to
-
OCMUI-2379 Fix NodeCountInput skipped test
-
- To Do
-
- relates to
-
-
- In Progress
-
- split to
-
-
- Closed
-
-
-
- Closed
-
- links to
- mentioned on
