Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 1. Introduction to the Red Hat Enterprise Linux software certification
The Red Hat Enterprise Linux Software Certification Policy Guide describes the policy overview to certify third-party vendor products running on Red Hat Enterprise Linux (RHEL) 8 and 9.
This guide is intended for partners who want to offer their products for use with RHEL in a jointly supported customer environment. A strong working knowledge of RHEL is required.
1.1. Certification prerequisites
To start your certification journey, you must:
- Join the Red Hat Partner Connect program.
- Accept the standard Partner Agreements along with the terms and conditions specific to containerized software.
- Enter basic information about your company and the products you need to certify. Common information includes a product overview and links to supporting collateral such as product documentation, datasheets, or other relevant resources.
- Support RHEL as a platform for the product being certified and establish a support relationship with Red Hat. You can do this through the multi-vendor support network of TSANet, or through a custom support agreement.
Additional resources
1.2. Test suite lifecycle
Use the latest version of the test suit to certify your products.
After the release of a new test suite version, Red Hat accepts test results generated with the earlier version of the suite for a period of 90 days. During this period, the Red Hat certification team may require you to run the tests with the latest version of the suite if they consider that it is more suitable for your certification project.
Additional resources
1.3. Red Hat Enterprise Linux versions and architecture
A Red Hat Enterprise Linux software certification is architecture-specific and does not carry over to any other architecture. You must certify your product on each version and architecture of RHEL that it supports.
The following table shows the RHEL versions, processor architectures, and hypervisor software that can you can combine in a certification:
| RHEL version | Architecture | Hypervisor |
|---|---|---|
|
|
|
|
Red Hat grants RHEL software certifications on specific RHEL 8 or RHEL 9 minor versions. The certification is valid for subsequent minor releases of RHEL if you follow the compatibility guidelines documented in the Red Hat Enterprise Linux: Application Compatibility Guide.
Red Hat recommends partners to retest their products with each new minor version of RHEL.
1.4. Partner’s product versions
Red Hat grants RHEL software certifications to specific major releases of your product. You should run the certification tests on minor releases of the product to avoid functional regressions, but you do not need to certify the product again.
You must certify subsequent major releases of the product either as a new version of the existing product or as a new product entry.
It is your responsibility to decide which releases of their product are major and which releases are minor.
1.5. Packaging format
Products targeted for certification can use any packaging format provided it does not alter the RHEL platform in a way that impacts its support. Red Hat recommends that you use packaging formats compatible with the platform’s native tools, such as containers and RPMs.
Any components packaged as containers must follow the requirements established in Container image requirements.
1.6. Catalog entries
Red Hat expects that a RHEL software certification remains listed in the catalog until the end of support life for the certified RHEL version. However, Red Hat reserves the right to remove a catalog entry.
1.7. Distribution of certified container images
The Red Hat Container Certification program offers the following options for the distribution of certified container images:
- Red Hat Container Registry: Managed by Red Hat at no cost to partners. This option requires compliance with U.S. export control laws. For more information, see the Export compliance guide.
- Non-Red Hat Container Registry: For example, your own registry, or any public registry such as Quay.io and Docker.io.
