CAPI Release Framework: Migrating Default-Apps

[Rotfuks]

Motivation

After we defined and aligned on an initial release framework for CAPI with #2522 we now have to continue our efforts to actually implement the target state we defined for the release framework. For this we need to align the structure of how and where we organise apps throughout all CAPI providers. In this epic we want to align all providers on migrating apps from default-apps charts to the provider independent cluster or provider specific cluster- chart.

Migration on AWS

Beta Give feedback

1. Design Helm values for App CRs in cluster and cluster-aws #3299
   area/kaas team/turtles +2
   
2. Migrate apps from default-apps-aws to cluster chart #3119
   Ready area/kaas team/turtles +3
   
3. Migrate apps from default-apps-aws to cluster-aws chart #3300
   area/kaas team/turtles +2
   
4. Adapt GS tooling to the removal of default-apps-aws #3419
   area/kaas team/turtles topic/capa-migration +3
5. Update docs on how to apply CAPA clusters #3120
   Ready area/kaas team/turtles +3
   

Migrating the rest

Beta Give feedback

1. Migrate apps from default-apps-azure #3122
   Ready area/kaas team/turtles +3
2. Migrate apps from default-apps-vsphere #3125
   Ready area/kaas team/tenet +3
   
3. Migrate apps from default-apps-cloud-director #3134
   Ready area/kaas team/turtles +3
4. Migrate apps from default-apps-eks #3561
   area/kaas team/turtles +2
5. Update docs on how to apply CAPZ clusters #3123
   Ready area/kaas team/turtles +3
   
6. Update docs on how to apply CAPV clusters #3126
   Ready area/kaas team/turtles +3
7. Update docs on how to apply CAPVCD clusters #3135
   Ready area/kaas team/turtles +3

Outcome

• We are aligned across all providers matching the documented release framework target state reducing complexity and onboarding friction.
• We decrease complexity for customers by reducing the number of charts to apply for a cluster creation or update to a single one.