feat(attest): CoCo dev-mode stack — pinned manifests, KBS topology decision - #9252
Conversation
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | 78cfa2c | Commit Preview URL Branch Preview URL |
Jul 27 2026, 10:35 AM |
Bundle ReportBundle size has no change ✅ |
❌ 17 Tests Failed:
View the top 3 failed test(s) by shortest run time
View the full list of 5 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
|
Caution 🛑 LoopOver review result - fixes requiredReview updated: 2026-07-27 10:32:02 UTC
Review summary Nits — 5 non-blocking
CI checks failing
Decision drivers
Context & advisory signals — never blocks the verdict
Linked issue satisfactionAddressed Review context
Contributor next steps
Signal definitions
🧪 Chat with LoopOverAsk LoopOver a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.
Full command reference: https://loopover.ai/docs/loopover-commands 🧪 Experimental — new and may change. Decision record
🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed 💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.
|
…cision (#9213) Vendors the Confidential Containers Helm chart (dev-only shim override) and Trustee KBS kustomize manifests in no-TEE dev mode, with every version pinned in versions.json and drift-checked in CI. Records the Trustee/KBS-mediated topology decision and the plan for recording real launch measurements once SNP hardware arrives, so #8536 becomes a config apply plus measurement recording on real metal. Verified against a real local kind cluster: the chart installs, the kata-qemu-coco-dev RuntimeClass is created, and the KBS manifests apply cleanly. Pod execution itself needs a real amd64 host (both the KBS image and the kata-deploy dev-shim daemonset are amd64/s390x-only); the attested-run harness (sample attester path) was verified standalone since it needs no Kubernetes/Kata/KBS at all.
a1fc68c to
78cfa2c
Compare
Summary
qemu-coco-devonly) and Trustee KBS kustomize manifests, digest-pinned, with aversions.jsonsingle source of truth drift-checked in CI (coco-dev-versions:check, wired intotest:ci).up.sh/down.shbring-up/teardown scripts;generate-kbs-keys.shmirrors upstream Trustee's own local-only key generation (never committed).Verified against a real local
kindcluster: the chart installs cleanly,kata-qemu-coco-devRuntimeClass is created, and the KBS manifests apply. Actual pod execution needs a real amd64 host (both the KBS image and the kata-deploy dev-shim daemonset publish amd64/s390x-only images — confirmed via genuineImagePullBackOff, not assumed); the attested-run harness (sample attester) was verified standalone since it needs no Kubernetes/Kata/KBS at all.k8s/coco-dev/README.mddocuments this boundary and why no recurring CI job or self-hosted runner was added for it.Closes #9213.
Test plan
npx vitest run test/unit/check-coco-dev-versions-core.test.ts— 10/10 passing, 100% statement/branch/function/line coverage on the new core modulenpm run coco-dev-versions:check— passes against the committed manifestsnpm run import-specifiers:check— passeskind create cluster+helm upgrade --installof the pinned chart +kubectl apply -kof the KBS overlay — all genuinely exercised locallyscripts/attested-backtest-run.ts --attester sample— runs to completion,{"status":"attested",...}, exit 0