As a HyperShift engineer, I want to investigate what Cluster API (CAPI) and CAPI provider upgrades are required for Kubernetes v1.33 compatibility, so that we can plan and execute the necessary dependency updates for HyperShift.

Acceptance Criteria

• Identify the minimum CAPI version required for Kubernetes v1.33 compatibility
• Document CAPI provider versions needed for each supported platform (AWS, Azure, PowerVS, KubeVirt, Agent, OpenStack)
• Identify any breaking API changes in CAPI that affect HyperShift
• Document any migration steps or code changes required in HyperShift
• Create follow-up epics and stories for each CAPI/CAPI provider upgrade identified as necessary*

Platforms to Investigate

• AWS (CAPA - Cluster API Provider AWS)
• Azure (CAPZ - Cluster API Provider Azure)
• PowerVS (CAPP - Cluster API Provider PowerVS)
• KubeVirt (CAPK - Cluster API Provider KubeVirt)
• Agent (CAPI Agent provider)
• OpenStack (CAPO - Cluster API Provider OpenStack)

Key Questions to Answer

• Are there any provider-specific version requirements?
• Are there breaking changes in CAPI controller contracts?
• Do we need to update our usage of CAPI APIs?
• Should the upgrade work be split into separate epics/stories per provider or combined?