Update CI configuration in Merge Request template
What does this MR do and why?
Update CI configuration in Merge Request template
Add ha option on all scenarios that will trigger a rolling upgrade with rke2 provider, as it does not support yet rolling upgrades on single control-plane node deployments.
Related reference(s)
This issue was observed here: !2062 (comment 2307740435)
Test coverage
CI configuration
Below you can choose test deployment variants to run in this MR's CI.
Click to open to CI configuration
Legend:
| Icon | Meaning | Available values |
|---|---|---|
| Infra Provider |
capd, capo, capm3
|
|
| Bootstrap Provider |
kubeadm (alias kadm), rke2
|
|
| Node OS |
ubuntu, suse
|
|
| Deployment Options |
light-deploy, oci, ha, misc
|
|
| Pipeline Scenarios |
rolling-update, mgmt-rolling-update, k8s-upgrade, sylva-upgrade, sylva-upgrade-from-x.x.X, simple-update, preview, nightly
|
-
🎬 preview☁️ capd🚀 kadm🐧 ubuntu🛠️ oci -
🎬 preview☁️ capo🚀 rke2🐧 suse -
🎬 preview☁️ capm3🚀 rke2🐧 ubuntu -
☁️ capd🚀 kubeadm🛠️ light-deploy🐧 ubuntu -
☁️ capd🚀 rke2🛠️ oci,light-deploy🐧 suse -
☁️ capo🚀 rke2🛠️ oci🐧 suse -
☁️ capo🚀 kadm🛠️ oci🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capo🚀 kadm🎬 k8s-upgrade🐧 ubuntu -
☁️ capo🚀 rke2🎬 mgmt-rolling-update🛠️ ha,misc🐧 suse -
☁️ capo🚀 rke2🎬 sylva-upgrade🛠️ misc🐧 ubuntu -
☁️ capm3🚀 rke2🐧 suse -
☁️ capm3🚀 kadm🛠️ oci🐧 ubuntu -
☁️ capm3🚀 kadm🎬 mgmt-rolling-update🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 rke2🎬 k8s-upgrade🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capm3🚀 rke2🎬 sylva-upgrade🛠️ misc,ha🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 suse
Be aware: after configuration change, pipeline is not triggered automatically.
Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.