Skip to content

docs(adrs): add technical proposal for Loki logging on OAC workload clusters - #1

Open
schwesig wants to merge 8 commits into
mainfrom
fm/ops-docs-logging-adr
Open

schwesig wants to merge 8 commits into
mainfrom
fm/ops-docs-logging-adr

Conversation

@schwesig

@schwesig schwesig commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner

What Changed

  • Added a new ADR (adrs/2026-10-19-workload-cluster-logging/README.md) containing a 292-line technical proposal covering six open decisions for the Loki logging stack on OAC clusters: storage class for LokiStack volumes, placement (per-cluster vs. central vs. hybrid), retention periods, long-term audit archival to S3 Object Lock, sizing, and environment separation.
  • The proposal documents the current implementation in OA_oac-apps/pull/2 as a starting point, calls out two departures from Red Hat support statements (NFS storage, 90-day audit retention), and lists 17 open questions for storage, network, compliance, and platform owners.
  • Updated package-lock.json package name field (minor correction from a prior restore commit).

🤖 Generated with Claude Code

Risk Assessment

✅ Low: The only change is a single-sentence reword in the "See also" section that adds the explicit repository name and "(not yet merged)" qualifier to a cross-repo PR reference, exactly as the user authorized.

Testing

Docs-only change: verified the recorded fix was applied exactly — the ambiguous PR 37 reference now names the upstream repo explicitly in plain words with no URL or shorthand. No executable surface exists to drive live.

  • Live validation: ⚠️ no-surface - 0 of 1 scenarios driven live against the product
Scenario Result Live Evidence
See-also line names the upstream repo explicitly without a URL or shorthand ⏸️ untested no This is a natural-language documentation change in a Markdown ADR file. There is no executable consumer, renderer, or validator that can be invoked to prove the wording is correct; the only validation…
  • Outcome: ⚠️ 1 warning across 1 run (29.5s)

Rendered technical proposal page (full page, headless Firefox)
ADR index listing the technical proposal

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

🔧 **Review** - 1 issue found → auto-fixed ✅
  • ⚠️ adrs/2026-10-19-workload-cluster-logging/README.md:268 - Line 268 references 'the per-project metrics ADR in ops-docs pull request 37'. The fork schwesig/ops-docs currently has only PRs 2, 3, and 4 open. PR 37 does not appear to exist in the fork. If this refers to the upstream CCI-MOC/ops-docs repo, the reference should name the repo explicitly (the intent prohibits work on CCI-MOC, which would make a cross-repo reference confusing). If it refers to a future PR not yet opened in the fork, the reference will be a broken link until that PR exists. Please confirm whether PR 37 exists or should be updated.

🔧 Fix applied.
✅ Re-checked - no issues remain.

⚠️ **Test** - 1 warning
  • ⚠️ this change has no live-validatable surface; proceed without live validation? (0 of 1 scenarios were driven live against the product); See-also line names the upstream repo explicitly without a URL or shorthand: This is a natural-language documentation change in a Markdown ADR file. There is no executable consumer, renderer, or validator that can be invoked to prove the wording is correct; the only validation surface is reading the file, which is not a live product surface.
  • Live validation: ⚠️ no-surface - 0 of 1 scenarios driven live against the product
Scenario Result Live Evidence
See-also line names the upstream repo explicitly without a URL or shorthand ⏸️ untested no This is a natural-language documentation change in a Markdown ADR file. There is no executable consumer, renderer, or validator that can be invoked to prove the wording is correct; the only validation…
  • Read adrs/2026-10-19-workload-cluster-logging/README.md lines 262-272 to confirm line 268 contains the new wording: 'The per-project metrics ADR proposed upstream in the CCI-MOC ops-docs repository, pull request 37 (not yet merged)'
  • git diff 9c796539..7d4b480 --stat — confirmed only the ADR README was changed, 292 lines added (new file), no deletions outside the single line
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

Record the per-workload-cluster LokiStack design, with hosted API audit
collected on the hub, as Proposed. Two choices depart from Red Hat
support statements (Loki PVCs on NFS, 90-day audit retention) and are
listed as open points.
@schwesig schwesig closed this Oct 20, 2026
@schwesig schwesig reopened this Oct 20, 2026
Turn the workload-cluster logging ADR into the technical proposal tracked
as MOC-issues 633. It lays out storage, placement, retention, long-term
audit archive, sizing and environment separation as open decisions with
options, trade-offs and recommendations, plus questions for the storage,
network and compliance owners. Nothing is recorded as decided.
@schwesig schwesig changed the title docs(adrs): add proposed ADR for workload cluster logging docs(adrs): add Loki logging technical proposal for OAC workload clusters Oct 21, 2026
The document step's npm run rewrote the lockfile's name field to the
pipeline run id. That change is unrelated to the ADR.
@schwesig schwesig changed the title docs(adrs): add Loki logging technical proposal for OAC workload clusters docs(adrs): add technical proposal for Loki logging on OAC workload clusters Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant