See full summary at https://docs.google.com/document/d/1xaZ20AyC7P--sAW3FNsfOmCvOe7o1k05V8sLexuklL0/edit?tab=t.0 

The Core Problem is a misalignment between the OCP catalog bootstrapping schedule and the RHWA Konflux release cadence. OCP catalogs are bootstrapped from the previous version's catalog (usually 2-3 weeks after the previous OCP branches out). If an RHWA operator package hasn't had its first release via Konflux before the bootstrap, the package is considered "not opted-in," and the catalog falls back to including all historically supported bundles, resulting in old, unsupported versions being included.

The Example of the node-healthcheck-operator shows OCP 4.21 and 4.22 catalogs incorrectly containing versions as old as v0.3.1 and v0.4.1, which are unsupported.

Recommended Solutions are:

1. Immediate Action (OCP 4.21): Release an interim RHWA FBC catalog update for OCP 4.21 before its GA date (Feb 3, 2026) to clean the catalog of old versions and fill the 2-week gap before the main RHWA-4.21-0 release.
2. Mid-term Action (OCP 4.22): Release the full, updated RHWA FBC catalog for OCP 4.22 to coincide with the main RHWA-4.21-0 release (Feb 17, 2026). This pre-emptive update ensures future catalogs (4.23+) bootstrap from a corrected catalog.
3. Strategic Alignment: For all future RHWA releases, ensure the Konflux release coincides with or precedes the OCP bootstrap day for the corresponding index.