Goal

• Set the InfrastructureAvailabilityPolicy to HighlyAvailable by default in the HyperShift v1beta1 API
• Set the InfrastructureAvailabilityPolicy to HighlyAvailable by default in both the HyperShift and HCP CLI

Why is this important?

• This is important in cases such as compact HCP. When the InfrastructureAvailablityPolicy is set to Single, it causes issues such as:

• • VMs not properly live migrating on node drains/upgrades
    • Per VM PDBs are never created
    • VMs are forcefully restarted on cluster upgrade
  • Virt component replicas are not scaled to total node count – this can lead to Virt control plane delays under load
• We should also keep consistency between InfrastructureAvailabilityPolicy and 
  ControllerAvailabilityPolicy (which is currently set to HighlyAvailable

Scenarios

1. ...

Acceptance Criteria

• Dev - Has a valid enhancement if necessary
• CI - MUST be running successfully with tests automated
• QE - covered in Polarion test plan and tests implemented
• Release Technical Enablement - Must have TE slides
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>