Epic Goal

• Update our CI, deployment, docs, etc. to use crun instead of runc.

Why is this important?

• OCP will change to use crun instead of runc for managing container processes in 4.13.
• We expect to see performance benefits using the new implementation (memory overhead, exec probe speed and overhead, etc.

Scenarios

The user should not perceive any difference and there will be no user-facing API changes.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Any documentation for configuring the system to use crun needs to be updated.
• Performance information comparing crun and runc should be collected and shared with the single-node OpenShift team.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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 - Downstream documentation merged: <link to meaningful PR>