Use CI values relative to specific versions into directories

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

What does this MR do and why?

This MR is a proposal for answering #1550 (closed)

This is based on CI values reorganization provided by sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!75 (merged).

CI values are now organized in different folders instead of branches:

  • one folder per specific versions (currently 1.1.1)
  • a folder current for values specific to main and dev branches
  • a folder common for all values usable in any case

The function update_values_file evolves for being able to search for applicable file(s).

  • If provided file exists, it merges it to values
  • Otherwise if the file can be found in CI common values, it merges it to values or/and if the file can be found in versioned files, it merges it to values

Related reference(s)

CI configuration

CI pipelines perform an update for both management and workload clusters, this update will NOT perform a ClusterAPI rolling upgrade (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-feature::test-rolling-upgrade 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)
Edited by Médéric de Verdilhac

Merge request reports