Kubernetes reference chart: add a Casework status operation and an optional BReg metrics port

Offen
#2,756 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
helm, json, kubernetes, rust, yaml

Rechercherichtung

Start in deploy/helm/registry-stack/: read values.schema.json for the casework.operation.kind enum, then the Job template that renders those kinds, and copy the existing BReg operation path for a status kind. For the metrics port, read crates/registry-breg/src/runtime_config.rs to see how metricsListener is parsed, then wire an optional (default-off) container and Service port plus a NetworkPolicy ingress rule limited to a configured scraper selector. Finish by extending the chart's existing contract tests and correcting the README sentence near line 485 that claims BReg exposes no metrics port.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:breg area:casework enhancement

From the review of #2742, the Kubernetes reference chart under deploy/helm/registry-stack/. The chart is an unsupported reference, so neither gap blocks anything.

1. No Casework status operation

caseworkctl has a status command, but the chart's Casework operation kinds are only plan, apply and doctor (values.schema.json, the casework.operation.kind enum). An operator cannot read Casework status through the same operation Job path used for BReg.

Expected: add status to the enum and the template, with a contract test, or say in the README why it is left out.

2. No BReg metrics port

BReg reads a metricsListener runtime setting (crates/registry-breg/src/runtime_config.rs), but the chart has no container port, Service port or NetworkPolicy rule for it. An operator who sets metricsListener in the runtime configuration cannot scrape it. The README (around line 485) says BReg "exposes no metrics port". That is inaccurate: BReg has a metrics listener, and only the chart does not expose it.

Expected: an optional metrics port (off by default) with a NetworkPolicy ingress rule limited to a configured scraper namespace or Pod selector, and a contract test. Or document that metrics are not wired in the reference and correct the README sentence.

Related: #2749 (metrics follow-ups).

Vorherrschende Sprache
Rust
Sterne
2
Forks
0
Ø Merge
9 Std. 48 Min.
Gemergte PRs (30 T.)
151

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus registrystack/registry-stack

Alle Issues in registrystack/registry-stack

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.