Red Hat OpenShift Container Platform (RHOCP) innovates at a rapid pace. The Red Hat OpenShift Container Platform Lifecycle Policy reflects this innovation. Approach OpenShift and certification testing through a continuous process to ensure ongoing interoperability and support for customers.

You must recertify your products in the following scenarios:

• Certifying another version of your product.
• Making another version of your product available through a Red Hat in-product software catalog (index, registry, or repository).
• Supporting another version or architecture of RHOCP.
• Making a material change to the product build, installation, upgrade process, or adding new functionality.
• Your product contains a critical Common Vulnerability and Exposure (CVE) that is older than 3 months.
• Your product contains an important CVE that is older than 12 months.
• Your product was certified more than 12 months ago.

Note

A product component with a Container Health Index grade of ‘A’ through ‘C’ meets the CVE requirements.

A material change is any change that alters the outcome of certification testing, impacts the customer experience of your product on OpenShift, impacts the customer experience of OpenShift, or impacts the customer ability to use any part of their Red Hat subscription(s).

Red Hat provides multiple mechanisms to monitor certified containers for critical vulnerabilities. This allows you to continuously monitor and identify for critical vulnerabilities. These mechanisms will help you determine when to rebuild and recertify.