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

Offen
#2,755 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
58/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
helm, kubernetes

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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).

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.