AWS vintage migration to CAPA implementation (Phase 1)

[alex-dabija]

Story

-As a cluster admin for vintage AWS clusers, I want to migrate existing clusters to Cluster API for AWS (CAPA) in order to benefit from all the new features Giant Swarm is developing as part of Cluster API (CAPI).

Background

Giant Swarm is moving all it's product AWS development to Cluster API (CAPI) and it has a lot of Vintage clusters which need to be migrated.

Scope

Beta Give feedback

1. CAPA SR release #2726
   15 of 15
   area/kaas kind/epic provider/cluster-api-aws team/planeteers topic/capi +5
   
2. https://github.com/giantswarm/giantswarm/issues/27910
3. https://github.com/giantswarm/giantswarm/issues/28148
4. Features required to migrate first customer

Hard dependencies

Beta Give feedback

1. CAPA Kubernetes 1.25 WC release #2925
   1 of 1
   area/kaas kind/epic team/null team/phoenix +4
   
2. AWS WC Release 20.0.0 #2862
   capi/migration provider/aws team/phoenix topic/aws-vintage topic/capa-migration +5
   
3. https://github.com/giantswarm/giantswarm/issues/28500
4. Backport Cilium fixes for ENI mode and default network policies feature #3005
   goal/capa-internal-ga team/phoenix +2
   

[puja108]

dupe of #309 ?

[alex-dabija]

Yes, it's a duplicate of #309, but I'll keep this one.

[alex-dabija]

We don't have much information at the moment on who we are going to approach the migration. We need to first talk about it in Phoenix and Hydra do decide on how to move forward.

We might need to also split the work:

• Customer Work for migration
• Technical Work for migration