Summary

The OpenShift Releases page at https://console.redhat.com/openshift/releases only displays 6 OCP versions (currently 4.21 through 4.16), but there are more than 6 currently supported versions according to the official Red Hat Product Life Cycle data.

Problem

The number of supported OCP versions continues to grow due to:

• Extended Update Support (EUS) terms (Term 1, 2, 3)
• Extensions to existing lifecycle phases
• Longer support timelines for major releases

The current hardcoded limit of 6 versions prevents customers from seeing all their supported versions on this page.

Expected Behavior

All currently supported OCP versions should be displayed on the Releases page, matching the versions shown in:

• https://access.redhat.com/support/policy/updates/openshift#dates
• https://access.redhat.com/product-life-cycles?product=OpenShift%20Container%20Platform

Actual Behavior

Only 6 versions are shown (4.21 through 4.16), hiding older but still supported versions.

Root Cause

The limit is hardcoded in src/components/releases/index.tsx at line 37:

const versionsToDisplay = filteredVersions?.splice(0, 6);

See: https://github.com/RedHatInsights/uhc-portal/blob/0cfc2b2ec1dfacfd7c5f1ec8f968bd89dee62501/src/components/releases/index.tsx#L37

Proposed Solution

Increase the limit from 6 to at least 8 (short-term), with consideration for 12 or 16 (long-term) given:

• Future OCP 5.x releases
• Continued support for OCP 4.x versions during transition
• Growing number of lifecycle phases and extensions

References

• Red Hat Product Life Cycle Policy: https://access.redhat.com/support/policy/updates/openshift#dates
• Product Life Cycle Center API documentation: https://docs.redhat.com/en/documentation/red_hat_product_life_cycle_data_api/1.0/html-single/red_hat_product_life_cycle_data_api/index
• Source code: https://github.com/RedHatInsights/uhc-portal/blob/0cfc2b2ec1dfacfd7c5f1ec8f968bd89dee62501/src/components/releases/index.tsx#L37

Impact

Customers cannot see all supported OCP versions for their clusters, potentially causing confusion about upgrade paths and support status.