Kubernetes reference chart: add a Casework status operation and an optional BReg metrics port
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- helm, json, kubernetes, rust, yaml
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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).
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 151
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
registrystack/registry-stack 的其他 Issue
-
area:breg enhancement
难度 2/5 1-3 小时 新手友好度 65/100
registrystack/registry-stack#2765 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
registrystack/registry-stack#2761 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
registrystack/registry-stack#2743 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
registrystack/registry-stack#2706 ·
维护者通常 1 天内回复
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directory未关闭
难度 2/5 1-3 小时 新手友好度 83/100
registrystack/registry-stack#2704 ·
维护者通常 1 天内回复
查看 registrystack/registry-stack 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 82/100
stackabletech/airflow-operator#898 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)可能已有人在做 @zyl71 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100