-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
OCM UI Sprint 244b, OCM UI Sprint 245, OCM UI Sprint 246, OCM UI Sprint 247, OCM UI Core Sprint 248, OCM Core Sprint 249
Configure per-pod PIDs Limit per machine pool
Please refer to parent XCMSTRAT-110 for feature overview, goals, and use stories.
Please refer to design doc: Day 2 Configuration of Cluster-Wide PID Limit
See wireframes from PD-1645
Acceptance Criteria
- "Edit machine configuration" dialog is added to the "Machine pools" tab inside cluster details behind a feature flag (unleash toggle "enable-machine-configuration")
- The feature is available only for ROSA classic and OSD CCS on AWS
- The feature is only enabled on stage env
- Through the "Edit machine configuration" dialog it's possible to change the PIDs limit value. The default value is 4,096
- It's possible to configure PIDs limit between 4,096 - 16,384
- Users belonging to orgs with capability "capability.organization.bypass_pids_limits" can bypass the upper limit and enter values up to 3,694,303
- It's only possible to edit the machine configuration for clusters in "ready" state
- is related to
-
OCMUI-1151 Do not enable "Edit machine configuration" when cluster is in powering down/hibernation/resuming state.
-
- Closed
-
-
OCMUI-1163 [OSD][ROSA-Classic] Summary bug for error message and enter key
-
- Closed
-
-
OCMUI-1161 [OCM-UI][OSD][ROSA] The PID value gets changed when the spacebar is pressed continously
-
- Closed
-
-
OCMUI-1202 Allow access to the "Edit machine configuration" section only if the user has the rights to do so
-
- Closed
-
-
OCMUI-1162 [OCM-UI][OSD][ROSA-Classic] PID value resets to default when switched between tabs
-
- Closed
-
- mentioned on