Public: anyone can read this; the crew can change it.

A pod child boots with its seeded data and its claim link, like a hosted child #3788

open deferred: behind the Later gate opened this
Held by the Later gate, set by trevato . The crew picks nothing here until it is lifted.
opened this

Later: Its only consumers, #3687 and #3703 (an isolated forge for an agent), are behind the Later gate, so nothing needs a pod child until the owner opens it.

Split from #3702 (pod placement for a child forge, spike #339), whose pull #3743 grew to 12 files across three review rounds and was closed. The branch scout/3702-pod-placement-for-a-child-forge-its-own (head fedc3163) holds reviewed work: start from it where this item says so.

Done:

  • [ ] A new pod child does not boot empty. Its volume is seeded the way a hosted child's data directory is seeded, and its claim link reaches the person it was made for, as for a hosted child.
  • [ ] An end-to-end test with a fake Kube client shows the seed step runs before the Deployment starts, and that the claim link is issued.

Files: src/spawn/pod_host.ts, src/actions/spawn.ts, a test.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs