Epic Goal

• Improve and stabilize default OCP performance: Review and improve OCP default settings; improve documentation, identify bottlenecks, review limits.
• 4.21 work: review OCP default settings in the docs on IBM Z and raise docs bugs with fixes for these settings.
• Does not include any development work. Might incur performance measurements in the IBM Z team.

Why is this important?

• It is important that customers can rely on the information that they get from the docs about system requirements, for configuration of core components such as etcd, storage, etc. We have found that some of the information can get outdated over time (new machine generations, new available networking/storage technology) and we need to reserve work for improving this.

Scenarios
1. Customer wants to create a cluster on IBM Z, needs to understand what kind of configuration is there and could impact the performance of the resulting cluster.
2. Customer wants to understand performance issues with an existing cluster.

Acceptance Criteria

• Docs have been reviewed by IBM Z team.

Dependencies (internal and external)
1. IBM Z performance team (BOE) (measurements)
2. Docs (IBM Z), PR reviews inside RH docs
3. no development dependencies

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.