Kubernetes reference chart: run the Evidence check Job with --require-runtime-dependencies and --require-audit-under

未关闭
#2,755 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
58/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
helm, kubernetes

调研方向

Start with deploy/helm/registry-stack/templates/evidence-operation-job.yaml around line 86 and the README paragraphs around lines 487-493, then check the chart's kubeVersion floor. Decide with the maintainer whether the floor can move to 1.29; if so, render the chart and confirm the check Job has the Transit proxy as a native sidecar with restartPolicy: Always plus both required flags, and add the contract test. Done means the rendered Job and README agree, or the README states /ready is the dependency gate.

由索引模型根据 Issue 内容生成。

描述

area:evidence enhancement

From the review of #2742, the Kubernetes reference chart under deploy/helm/registry-stack/. The chart is an unsupported reference, so this does not block anything.

What happens

The Evidence check operation Job runs evidence check without --require-runtime-dependencies and --require-audit-under (templates/evidence-operation-job.yaml, around line 86). The chart README (around lines 487-493) explains why: a real dependency check needs the workload-local Transit proxy, and a long-running proxy container would stop a standard Job from completing on every Kubernetes version the chart supports (kubeVersion: ">=1.28.0-0").

So the Job does not prove the signer, sources, token issuer or audit placement before evidence.serve is turned on. The serving process and /ready check them later.

Possible fix

Kubernetes native sidecars (an init container with restartPolicy: Always) stop when the Job's main container exits. They are on by default from Kubernetes 1.29. If the chart floor moves to 1.29 or later:

  • run the Transit proxy as a native sidecar in the check Job,
  • add --require-runtime-dependencies and --require-audit-under <audit path> to the Job,
  • update the README paragraph and add a contract test that the rendered check Job has both flags and a sidecar with restartPolicy: Always.

If the floor stays at 1.28, say in the README that /ready is the dependency gate and close this.

Related: #2192 (the dependency check should name which dependency failed).

主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。