[release-1.3] Update Kubernetes patch versions to 1.30.9 and 1.29.13

Closes #2100 (closed)

This MR upgrades patch versions for Kubernetes:

• 1.30.9 (from 1.30.7)
• 1.29.13 (from 1.29.11)

Additionally to the update initially computed by Renovate Bot, it updates the other parts of sylva-units that need to align with these versions.

In particular the calico and ingress-ngninx chart version are aligned with the ones used in newer RKE2, consistently with:

• https://github.com/rancher/rke2/blob/v1.30.7%2Brke2r1/charts/chart_versions.yaml vs https://github.com/rancher/rke2/blob/v1.30.9%2Brke2r1/charts/chart_versions.yaml
• https://github.com/rancher/rke2/blob/v1.29.11%2Brke2r1/charts/chart_versions.yaml vs https://github.com/rancher/rke2/blob/v1.29.13%2Brke2r1/charts/chart_versions.yaml

An evolution brought in ingress-nginx 1.12 restricts the allowed characters in an ingress path, preventing the use of . that is currently present in the Ingresses defined by the os-image-server component. To work around this, ingress-nginx configuration for the mgmt cluster is changed to disable this check (which in our case isn't creating a significant security risk since end users do not create ingresses on the mgmt cluster): strict-validate-path-type: false.

---

This MR contains the following updates:

Package	Update	Change
sylva-projects/sylva-elements/diskimage-builder	patch	0.3.9 -> 0.3.11

---

Release Notes

• upgrade Kubernetes to patch versions 1.30.9 and 1.29.13 !338
• [backport-0.3] update cloud init version for ubuntu jammy 22.04 !348

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot Sylva instance.

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, dev-sources, ha, misc
🎬	Pipeline Scenarios	Available scenario list and description

• 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu

• 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

• 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

• ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

• ☁️ capd 🚀 rke2 🛠️ light-deploy 🐧 suse

• ☁️ capo 🚀 rke2 🐧 suse

• ☁️ capo 🚀 kadm 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capo 🚀 kadm 🎬 wkld-k8s-upgrade 🐧 ubuntu

• ☁️ capo 🚀 rke2 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 suse

• ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.2.1 🛠️ ha 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🐧 suse

• ☁️ capm3 🚀 kadm 🐧 ubuntu

• ☁️ capm3 🚀 kadm 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 wkld-k8s-upgrade 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 ubuntu

• ☁️ capm3 🚀 rke2 🎬 sylva-upgrade-from-1.2.1 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse

Global config for deployment pipelines

• autorun pipelines
• allow failure on pipelines

Notes:

• Enabling autorun will make deployment pipelines to be run automatically without human interaction
• Disabling allow failure will make deployment pipelines mandatory for pipeline success.
• if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

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.

⚙️ If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)