apply healthchecks to more Keycloak OIDC custom resources (!8332) · Merge requests · Sylva-projects / sylva-core

This MR:

applies healthchecks to more Keycloak OIDC custom resources
fixes some existing healtchecks (were healthChecks were pointing to the OIDC client, but this was ineffective because not healthCheckExprs was defined to adjust to the peculiarities of the status of the CRDs)

To achieve this, this MR moves the healthCheckExprs that we already had in a unit-template, to make them more elegantly reused: since unit-templates lists and lists coming from a unit definition are concatenated, we can easily mix healthCheckExprs local to a unit with healthCheckExprs shared with other units. This was important to cover vault-oidc-init in this MR in a clean way.

Another side-effect change was brought: some healthChecks were done on the Secret produced by an OIDC client, which made sense when we had no way of checking the OIDC client resource status ; it was the case when those healthChecks were added, but since we here generalize the use of healthCheckExprs to properly check the OIDC client resource status, it actually much better to check the status of the OIDC client (checking only the Secret presence tells us nothing in an upgrade scenario where the Secret would be updated).

This MR also prepares ground for doing the same for checking ExternalSecrets, with the perspective of not having to list in healthChecks the Secrets that are a byproduct of an ExternalSecret, which will then allow in many cases to not have to list anything in healthChecks, with the benefit of checking more resources (today, as soon as we set healthChecks, we prevent Flux from status-checking resources not explicitly listed and that it would look at with wait: true).

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 Jun 24, 2026 by Thomas Morin

apply healthchecks to more Keycloak OIDC custom resources

CI configuration

Global config for deployment pipelines

Merge request reports