Undefined Epic Goal
While t-shirt sizing can have some complexities around validating requests are sufficient and accurate, a high value achievement is to change the ACM/MCE installer so no memory limits are written into components managed by the installer. This would comply with OpenShift best practices (but not industry workload best practices).
See https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#resources-and-limits for some additional details.
- This does not need to be optional, we could remove these limits by default
- Whether limits for CPU should be removed is TBD
Why is this important?
If a customer runs out of memory with a pod, we don't always have a good answer for how they can change the limit. The t-shirt sizing answer may help, but it may have some disadvantages too. If t-shirt XL has no limits, this forces the customer to use that size to remove a limit(s) they didn't want, when maybe they could run with a small/medium sized hub in general.
Scenarios
For what the Installer can control on the hub, remove the memory limits. There will still be operators that control their own resources the installer doesn't interact with.
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.