Define grafana roles via keycloak-user-management (!8284) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Into previous implementation we had issues related to roles definition:

drift detection, due to annotation field which is defined via keycloak user management chart, once the resource is applied crossplane provider handle this resourse and change the initial state, leading to inconsistence
sso test failed, no proper roles applied, change the role name comparing with those ones expected by grafana (( 'grafanaadmin') && 'Admin' || contains(roles[], 'grafanaeditor') && 'Editor' || contains(roles[], 'grafanaviewer') && 'Viewer)

roles:
  grafanaeditor-role: <= role name used to defined the resource in both k8s & keycloak 
    externalName: sylva/grafanaeditor <= annotation set on helm chart level
    description: "Editor role for Grafana"

And the manifest generated by the chart will be:

# Source: keycloak-user-management/templates/roles.yaml
apiVersion: role.keycloak.m.crossplane.io/v1alpha1
kind: Role
metadata:
  name: grafanaviewer-role
  namespace: default
  annotations:
    crossplane.io/external-name: sylva/grafanaviewer <= annotation from helm chart values
    // crossplane.io/external-name: 793de597-1ebf-461c-8038-b6b43e116d53 <= resource applied and new external-name is set,
       generate the conflict between flux controller and crossplane 
spec:
  forProvider:
    realmId: "sylva"
    name: grafanaviewer-role => role name on keycloak name
    //  name: grafanaviewer => expected value 
    description: "Viewer role for Grafana"
  providerConfigRef:
    name: keycloak-provider-config
    kind: ProviderConfig
  managementPolicies:
    - "*"

The scope of this MR is to configure the grafana roles but this time being complient with grafana requirements.

This MR depends on:

sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!441 (merged) ( CI values)
sylva-projects/sylva-elements/helm-charts/keycloak-user-management!17 (merged) ( keycloak-user-management helm chart)

Closes #4232 (closed).

Test coverage

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 18, 2026 by Bogdan Antohe

Define grafana roles via keycloak-user-management

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports