Apply specific files for capm3 sylva upgrade scenario

Médéric de Verdilhacrequested to merge
Fix_capo_sylva_upgrade into main

What does this MR do and why?

!3203 (merged) generates side effect on capo sylva upgrade CI pipeline by applying some capm3 specific file to capo config.

This MR fixes this by specifically applying needed CI values on cpam3 run only.

Related reference(s)

Test coverage

CI configuration

CI pipelines perform an update for both management and workload clusters, this update will NOT perform a ClusterAPI rolling update (deletion and creation of new K8s nodes) by default.

For some cases, it may be relevant to perform more complex tests.

Theses features can be activated in an MR by adding one of these labels to the MR and will apply to the next pipelines.

  • adding the label ci-featuretest-rolling-update pipelines will perform a node rolling update in the -update jobs (without version upgrades)
  • adding the label ci-featuretest-upgrade-from-1.1.1 pipelines will perform an upgrade from Sylva 1.1.1 to your dev branch (including a k8s version upgrade resulting in a node rolling update)

Merge request reports