feat/remote-egress #2

Merged

troed merged 15 commits from feat/remote-egress into main

2026-10-11 14:04:18 +02:00

troed commented

2026-10-11 14:04:03 +02:00

Owner

Adds opt-in egress for remote umwelt sandboxes.

umwelt_egress rule argument renamed host -> destination (breaking).
Remote agent permits egress, refuses ingress; remote-install --egress
provisions the gateway image, CA/bundle and install.json.
remote-install --egress records a durable [egress] floor; ctl's drift
check keys on it; re-provision upserts it.
Fully-qualify base image FROM lines (host short-name config varies).

Verified end-to-end against a real server: kubectl (full TLS verify) and
pgcli reach the target host's k3s API and Postgres, internet egress works,
unlisted destinations are denied.

Adds opt-in egress for remote umwelt sandboxes. - `umwelt_egress` rule argument renamed host -> destination (breaking). - Remote agent permits egress, refuses ingress; remote-install --egress provisions the gateway image, CA/bundle and install.json. - `remote-install --egress` records a durable `[egress]` floor; ctl's drift check keys on it; re-provision upserts it. - Fully-qualify base image FROM lines (host short-name config varies). Verified end-to-end against a real server: kubectl (full TLS verify) and pgcli reach the target host's k3s API and Postgres, internet egress works, unlisted destinations are denied.

troed added 15 commits

2026-10-11 14:04:03 +02:00

fix(host-actions): raise MAX_TIMEOUT 300 -> 3600 for long build actions 2c9d3cb82d

docs(spec): remote sandbox egress (rev 2 design) 9c69ec81f5

Extends the remote design: un-reduce the remote agent to the local egress
path, rename umwelt_egress's destination argument host -> destination,
opt-in server-side egress provisioning (remote-install --egress), and the
first-consumer reachability (static TCP to the host address, derived
kubeconfig, runtime tool installs).

docs(plan): remote sandbox egress implementation plan a7e1e6a649

chore: ignore .worktrees/ 2a4e487483

feat(egress)!: rename the rule argument host -> destination d23dcbaac4

Frees 'host' to mean the sandbox on every tool. The persisted config key
and EgressRule.host are unchanged.

feat(remote): permit egress, refuse ingress, in the remote agent 27ec7f7800

The remote front-end now starts the egress gateway and enforces egress
policy exactly as run.py does; ingress stays remote-refused.

fix(egress): name the remote remedy when server prerequisites are missing ac01c4348b

feat(remote): opt-in server-side egress install (remote --egress) 92b3678661

Builds the gateway image, CA, and install.json on the server and verifies
the egress prerequisites; the pushed tree now carries the gateway build
inputs.

feat(ctl): remote-install --egress provisions a server's egress prerequisites 67b7dfe465

fix(ctl): key the egress drift check on the durable [egress] opt-in record 00cad94bb4

fix(remote): upsert the [egress] floor on re-provision 8c58720e44

write_config returned early when the base config already existed, before
the [egress] append, so re-provisioning a server with --egress (or
retrying a half-finished install) recorded no egress opt-in - and
_verify_server_floor keys its egress drift check on that record, yielding
a false green on remote-status. Extract append_egress_section and call it
from the leave-alone branch too, guarded by a grep for an existing
[egress] header. Covered by
test_remote_install_egress_upserts_section_into_existing_config.

docs(readme): correct remote-targets egress routing 7bff164cc6

The remote-targets section listed the acting tools without egress and
claimed egress was a local management call whose host argument was the
policy target. Both are wrong: egress is remote-routable, and its rule
target is the destination argument (host is the sandbox selector). Add
egress to the acting-tools list, rewrite the sentence, and mention the
--egress provisioning flag in the provisioning paragraph.

test(remote): cover the remote egress remedy branches f6c5b80c99

- test_run: drive a real load_install_state failure (stale schema) so the
  remote path's str.replace of the local remedy is exercised (the prior
  test only reached the append fallback) and assert the substituted
  message, not a doubled remedy.
- test_agent: assert start_egress_gateway received remote=True instead of
  swallowing it in **kw.

docs(config): correct remote-targets egress routing 6214d0a953

Apply the README fix to CONFIGURATION.md's remote-targets section, which
carried the same two false claims: its acting-tools list omitted egress,
and it called egress a local management call whose host argument was the
policy target. egress is remote-routable; its rule target is the
destination argument and host selects the sandbox. The provisioning
section already documents --egress, so only these two statements change.

build: fully-qualify base image FROM lines (docker.io/library/...) dd490b8c2b

Host short-name alias/search config differs per machine (openSUSE maps some
names to registry.opensuse.org), so an unqualified FROM resolved differently
on a service account and failed the gateway build. Fully-qualified pulls are
deterministic on any host with network.

troed merged commit d8128f3e4e into main

2026-10-11 14:04:18 +02:00

troed deleted branch feat/remote-egress

2026-10-11 14:04:18 +02:00

troed referenced this pull request from a commit

2026-10-11 14:04:20 +02:00

feat/remote-egress (#2)