User Story:

As a customer, I want to be able to:

• Safely upgrade older clusters without breakage
• Have hosted CRs be automatically adapted to the expected new settings before upgrades
• Not run into issues like OCPBUGS-37486 - a cluster that was created with a set of older defaults was attempting an upgrade, but failed due to the older defaults breaking during the upgrade.

so that I can achieve

• Keep operating my application using Hypershift
• Access the cluster during upgrades

Acceptance Criteria:

Description of criteria:

• Hypershift regression tests cover HCP clusters with older HostedCluster CRs and settings

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• This is a follow up to OCPBUGS-37486 - the goal is to improve detection of these issues during testing, so Hypershift clusters don't break, just because they were created with a no-longer used set of defaults.
• The goal is mostly to improve regression tests around the possible combinations of settings, so we can proactively detect these before someone is running into them

This does not require a design proposal.
This does not require a feature gate.