Epic Goal

• The node team relies on many kernel APIs for the various operations it does. Specifically: runc, crun, cri-o and kubelet all directly communicate with the kernel. These APIs may change and these changes should be known about
• The goal of this epic is to find ways to increase collaboration between node team and kernel team to hear about new changes in the kernel.
• Compile a list of APIs Node team relies on
• Create test suites for those APIs
• Begin semi-regular meeting to discuss possible kernel changes in these areas.

Why is this important?

• In the bump to RHCOS 9, there were a number of issues found at the last minute. many of these changes happened years ago, and were only surfaced when testing began. Increasing communication between these teams will prevent this from happening as the product moves towards more major version releases.

Scenarios

1. As a member of the node team, I'd like to know about changes to the kernel APIs so I am prepared for updates to the major version of RHEL

Acceptance Criteria

• A list of kernel APIs the node team relies on must be created
• Plans for creating tests for those APIs should be created
• A regular meeting should be created between Kernel and Node

Dependencies (internal and external)

1. Kernel team

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>