Red Hat Extensions Repository Support Policy

Customer Benefits from the Extensions Repository

The Extensions repository will contain hand-picked upstream content that has gone through Red Hat’s Secure Supply Chain to ensure trust in its chain of custody. These packages will be “Known by Default”, meaning they will be consumable and manageable within the RHEL ecosystem, including Satellite, Insights and Image Builder. This repository, disabled by default, will contain only the latest software versions and is not tied to the RHEL release cadence, meaning new packages can be released at any time.

Red Hat Built and Trusted

Content in the Extensions repository has been built and signed by Red Hat ensuring that the RHEL user benefits from RPM metadata as well as CVE mitigation announcements.

Support Policy Overview

Red Hat supports customers using Red Hat Validated content with Red Hat platforms according to the Red Hat Third Party Component Policy. This means that there are no long-term lifecycle and/or ABI commitments for the extensions repository and Red Hat will ask the customer to reproduce the issue using a Red Hat certified or partner validated product. For further help on the issue, the customer will be directed to the third party.

See below for how the extensions repository fits in with other common content sources used with RHEL:

Note: To avoid possible conflicts, we recommend enabling either Extensions or EPEL, not both as packaging conflicts can be expected.