rancher logging/monitoring chart version updates compatible with rancher 2.11.x
closes #2660 (closed)
updating the rancher logging and monitoring helm charts to use the latest 106.x version compatible with k8s 1.32.x and rancher 2.11.x as there were some failures reported in logging with k8s 1.32.5 version
upgrade pipeline failing for logging due to compatibility issue of the chart version rancher-logging with version 105.3.1+up4.10.0-rancher.6
- https://gitlab.com/sylva-projects/sylva-core/-/jobs/10836339234
- https://gitlab.com/sylva-projects/sylva-core/-/jobs/10838554508
╰┄╴HelmRelease/sylva-system/logging InProgress HelmRelease generation is 2, but latest observed generation is 1
├┄╴┬┄┄[Conditions]
┆ ├┄╴Reconciling True Progressing Running 'upgrade' action with timeout of 5m0s
┆ ├┄╴Ready False UpgradeFailed Helm upgrade failed for release cattle-logging-system/logging with chart rancher-logging@105.3.1+up4.10.0-rancher.6: chart requires kubeVersion: >= 1.28.0-0 < 1.32.0-0 which is incompatible with Kubernetes v1.32.5+rke2r1
┆ ╰┄╴Released False UpgradeFailed Helm upgrade failed for release cattle-logging-system/logging with chart rancher-logging@105.3.1+up4.10.0-rancher.6: chart requires kubeVersion: >= 1.28.0-0 < 1.32.0-0 which is incompatible with Kubernetes v1.32.5+rke2r1
╰┄╴┬┄┄[Events]
├┄╴2025-07-28 21:12:45 (x76 over 10m2s) Normal DependencyNotReady unable to get 'sylva-system/root-dependency-2' dependency: helmreleases.helm.toolkit.fluxcd.io "root-dependency-2" not found
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, maxsurge-0, logging, no-logging
|
|
| 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🚀 kadm🐧 ubuntu -
☁️ capo🚀 rke2🛠️ ha,logging🐧 suse -
☁️ capo🚀 kadm🎬 wkld-k8s-upgrade🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update-no-wkld🛠️ ha🐧 suse -
☁️ capo🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha🐧 ubuntu -
☁️ capo🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha,misc🐧 ubuntu -
☁️ capo🚀 rke2🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 kadm🛠️ ha,logging🐧 ubuntu -
☁️ capm3🚀 kadm🐧 ubuntu -
☁️ capm3🚀 rke2🎬 wkld-k8s-upgrade🛠️ ha🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capm3🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha,logging🐧 suse -
☁️ capm3🚀 rke2🛠️ misc,ha🐧 suse -
☁️ capm3🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha,misc🐧 suse -
☁️ capm3🚀 kadm🎬 sylva-upgrade-from-1.4.x🛠️ ha🐧 ubuntu -
☁️ capm3🚀 ck8s🎬 no-wkld🛠️ light-deploy🐧 ubuntu
Global config for deployment pipelines
-
autorun pipelines -
allow failure on pipelines -
record sylvactl events
Notes:
- Enabling
autorunwill make deployment pipelines to be run automatically without human interaction - Disabling
allow failurewill make deployment pipelines mandatory for pipeline success. - if both
autorunandallow failureare 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.