|
81 | 81 | 6. A `GF_AUTH_GENERIC_OAUTH_CLIENT_SECRET` env on the Grafana |
82 | 82 | Deployment sourced from the Secret in step 4. |
83 | 83 |
|
84 | | -For the platform release (release name `monitoring-system`), the chart |
85 | | -sets `allow_assign_grafana_admin: true` so an `Admin`-group member is |
86 | | -auto-promoted to server-level `GrafanaAdmin` (necessary because the |
87 | | -platform Grafana serves as the meta-admin dashboard). Tenant Grafana |
88 | | -instances keep it `false` — organisation-level Admin is enough. |
| 84 | +Server-level `GrafanaAdmin` promotion is opt-in via |
| 85 | +`spec.oidc.grafanaAdmin: true`. When set, an `<clientId>-admin` group |
| 86 | +member is auto-promoted to `GrafanaAdmin` (via |
| 87 | +`allow_assign_grafana_admin: true` in the rendered `[auth.generic_oauth]` |
| 88 | +block). The platform bundle |
| 89 | +(`packages/core/platform/templates/bundles/system.yaml`) flips it on for |
| 90 | +the platform Grafana release via |
| 91 | +`Package.spec.components["monitoring-system"].values.oidc.grafanaAdmin: true`; |
| 92 | +tenant Grafana releases inherit the chart default `false` and stay at |
| 93 | +org-level Admin. |
89 | 94 |
|
90 | 95 | ## CustomConfig mode |
91 | 96 |
|
@@ -185,6 +190,16 @@ work — useful when Keycloak is down or misconfigured. |
185 | 190 | mappings** — Grafana rejects the callback and the login screen |
186 | 191 | shows an error; the `admin_user`/`admin_password` Secret keeps |
187 | 192 | working as break-glass. |
| 193 | +- **Mode toggle destroys chart-owned `KeycloakRealmGroup` |
| 194 | + membership.** The three groups (`<clientId>-{admin,editor,viewer}`) |
| 195 | + are release-owned. Flipping `spec.oidc.mode` from `System` to |
| 196 | + `CustomConfig` or `None` runs a `helm upgrade` that deletes the |
| 197 | + three `KeycloakRealmGroup` objects — and, with them, every user's |
| 198 | + membership. Flipping back to `System` recreates the groups empty; |
| 199 | + the platform operator has to re-populate them by hand (via the |
| 200 | + Keycloak UI or new `KeycloakRealmUser` CRs). Not a bug, but a |
| 201 | + one-way UX cost on the toggle; treat it like rotating an admin |
| 202 | + Secret. |
188 | 203 | - **`emailVerified` on Keycloak users is a prescriptive requirement, |
189 | 204 | not a chart-enforced one.** The chart does not emit any |
190 | 205 | `claimValidationRules` — the layered guarantees you rely on |
|
0 commit comments