Problem:
Team OCMUI reported styling differences between Production and Staging environments where text appears bold in Production but not in Staging. This affects the overview cards and other components across the platform.

Root Cause:
The issue is caused by different CSS load order of PatternFly styles between environments due to PF5 cutoff preparation:

• Staging: PF6 styles load first, then PF5 styles load after (due to PF5 cutoff preparation)
• Production: PF5 cutoff preparation not yet deployed

The problematic rule font-family: var(-pf-v5-globalFontFamily-text); overrides the PF6 font styles when PF5 CSS is loaded after PF6 CSS, which happens in staging because of the cutoff preparation.

Affected URLs:

• Overview page: https://console.redhat.com/openshift/overview vs https://console.dev.redhat.com/openshift/overview
• Cluster Details: https://console.redhat.com/openshift/details/s/38vZkPk592Ts0V7CWmsZwybtqQH#overview

Solution:
Implement CSS override rules to handle conflicts between PF5 and PF6 styles when both are loaded, ensuring consistent font rendering regardless of load order.

Impact:
More styling conflicts between PF5 and PF6 may surface as we approach the PF5 cutoff deadline.