Skip to content

Commit f7cec70

Browse files
committed
docs(monitoring): the per-tenant Grafana is also monitoring-system
Address review: the OIDC guide still said the tenant instance is released as `monitoring`. Both instances are `monitoring-system` (the inner HelmRelease is `{{ .Release.Name }}-system` and sets neither releaseName nor targetNamespace, so Flux defaults it), and only the namespace differs. Correct the sentence and join the paragraph into a single line per the file's one-line-per-paragraph prose convention. Signed-off-by: manon <[email protected]>
1 parent 4da6df5 commit f7cec70

1 file changed

Lines changed: 1 addition & 6 deletions

File tree

‎docs/oidc-grafana.md‎

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,6 @@
11
# OIDC for the Grafana instance (Phase 1)
22

3-
Cozystack ships one Grafana codebase deployed twice: as
4-
`monitoring-system` in the platform's `tenant-root` namespace and as
5-
`monitoring` in every tenant namespace. Both instances opt in to OIDC
6-
authentication through the same flat selector on the `Monitoring` CR.
7-
This document covers the operator-facing surface: what the modes mean,
8-
what the chart provisions, and how a user signs in.
3+
Cozystack ships one Grafana codebase deployed twice, both released as `monitoring-system` and differing only by namespace: the platform instance runs in `tenant-root` and a per-tenant instance runs in every tenant namespace. Both instances opt in to OIDC authentication through the same flat selector on the `Monitoring` CR. This document covers the operator-facing surface: what the modes mean, what the chart provisions, and how a user signs in.
94

105
The architectural rationale lives in
116
[cozystack/community#24](https://github.com/cozystack/community/pull/24)

0 commit comments

Comments
 (0)