Move from keycloak operator to keycloak chart (!7003) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Move of keycloak unit from operator to chart (this one: https://artifacthub.io/packages/helm/cloudpirates-keycloak/keycloak)

Changes:

Service keycloak-service becomes keycloak
Ingress keycloak-ingress becomes keycloak
Secret keycloak-bootstrap-admin is now managed by keycloak
KC_SPI_TRUSTSTORE_FILE_HOSTNAME_VERIFICATION_POLICY becomes KC_TLS_HOSTNAME_VERIFIER (https://www.keycloak.org/srver/all-config) (SPI_... - is the old naming convention on environment variables for keycloak)
Secret keycloak-internal-tls is the keycloak internal certificate that is handled by the internal Certificate Manager (from keycloak-internal-tls is created keycloak-tls secret)
If external certificate is provided, then truststore is enabled and keycloak-truststore secret is used by keycloak; (keycloak-operator used configmap keycloak-trustore - on upgrade this cm will remain available, but will not be used by the chart). The key from the external certificate is used for keycloak-tls secret, and truststore-password is the password used for the creation of truststore.jks file.

Upgrade scenario:

postgres DB content is preserved
access tokens preserved
cached data is lost

Closes #3081 (closed)

Test coverage

Tests in CI and local deployment in capo, in rocket.

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	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	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 (i.e `real-bmh` for capm3 )

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 May 13, 2026 by Cristina Isaroiu

Move from keycloak operator to keycloak chart

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports