feat: see the fleet and the runner, and rename the vault to fabrikk #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "omni-and-runner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Outcome
The factory can see the fleet and the runner it releases on, and its secrets live under one vault name.
What changed
extensions/models/forgejo_actions.ts:runner_list(read-only). It shows the org runnerdataverket-runner: a Kata VM pod indataverket-prod, labelsubuntu-latestandkata. Not thefabrikk-releaserunnerrelease.yamlassumes.models/@mccormick/omni/inventory/omni.yaml: read-only fleet discovery through a Reader service account. Today: one cluster, six machines, all connected.models/@swamp/kubernetes/pod/runner-pods.yaml: theforgejo-runnersnamespace over the Omni-issued kubeconfig (pairs with thefabrikk-readersRoleBinding PR in flux-bootstrap).forgejorenamed tofabrikk, file and model references updated; keys unchanged.Protected paths
Touches
models/,extensions/,README.md. No factory run behind this PR.Test plan
~/.swamp/deno/deno test --allow-all extensions/models/(39 passing)swamp vault list-keys fabrikklists both keys;swamp model method run forgejo healthgreen through the renamed vaultswamp model method run omni discoverrecordsdataverket-prodwith 3 control planes and 3 workers