documentation: fix Keycloak app version (!8725) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

CloudPirates released Helm chart keycloak version 0.21.10 twice:

date	upstream commit	chart	appVersion
2026-06-08 06:36	`3dc34a34a`	0.21.10	26.6.3
2026-07-13 08:44	`3e4c9d4f8`	0.21.10	26.7.0 — `version:` not bumped
2026-07-13 09:06	`706c820d4`	0.21.11	26.7.0 — mistake noticed, release continued

Publishing the second one overwrote the tag on docker.io at 2026-07-13T09:04:36Z (digest sha256:267851fc…, confirmed by Docker Hub tag_last_pushed). No released version carries 26.6.3 any more.

Sylva had mirrored 0.21.10 on 8 June, i.e. the 26.6.3 edition. Renovate merged the 0.21.10 pin to main on Thu 2026-07-30 18:07 (72915e902), so the Friday nightly was the first push-helm-artifacts run in verify mode to compare our artifact with upstream — mismatch, and it correctly refuses to overwrite a published artifact:

ValueError: [ERROR] keycloak content differs from the content of the already existing OCI artifact tools/oci/artifact_utils.py:107

I have deleted the 0.21.10 digest from the Sylva registry and re-pushed from current upstream, so mirror and upstream now match and the job passes.

We also need to update the unit description to match the new app version.

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`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

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.

Edited Aug 03, 2026 by Dragos Gerea

documentation: fix Keycloak app version

What does this MR do and why?

CI configuration

Global config for deployment pipelines

Merge request reports