Fix deployment-failure:cleanup job.

Loic Nicollerequested to merge
fix_capo_cleanup into main

What does this MR do and why?

Fix deployment-failure:cleanup job. Due to the merge of !2906 (merged) some variable are now defined in the job instead of being defined at gitlab-ci level. Theses variables are calculated during the before_script via .deployment-information. In the case of deployment-failure:cleanup the before script is overrided to add some commands.

So the cleanup script run with the default values of CAPO_TAG, resulting in no cleanup. This haven't be seen before as we have a scheduled pipeline that remove remaining stacks

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