Drew Newberry
0b6aa0f742
## Summary - Add a "push" path for local development that exports Docker images from the host daemon and imports them directly into the k3s containerd runtime, eliminating the need for a local registry or remote image pulls during `mise run cluster` - Add `mise run cluster:deploy` task for fast iterative rebuilds (~25s) against a running cluster without recreating it - Update `cluster-entrypoint.sh` to patch HelmChart manifest with local image tags and `IfNotPresent` pull policy when push mode is active ## Details Previously, after the local registry (k3d + skaffold) was removed, `mise run cluster` only pulled component images from the remote CloudFront registry. This meant local code changes required a remote publish cycle to test in-cluster. This MR adds a push path that sits alongside the existing pull path: - **`push.rs`** — Uses bollard to `export_images()` all 3 component images into a single tar (with shared layer dedup), uploads via Docker `put_archive` API into the cluster container, then runs `ctr images import` to load them into containerd - **`docker.rs`** — Passes `IMAGE_TAG` and `IMAGE_PULL_POLICY` env vars into the cluster container when `NAVIGATOR_PUSH_IMAGES` is set - **`lib.rs`** — Wires push into the deploy flow between `clean_stale_nodes()` and `wait_for_cluster_ready()`, guarded by `remote_opts.is_none() && NAVIGATOR_PUSH_IMAGES` - **`cluster-entrypoint.sh`** — Patches the baked-in HelmChart manifest with sed to use the local image tag and pull policy before k3s starts - **`cluster.toml`** — Updated `[cluster]` task to tag and push images; new `[cluster:deploy]` task for iterative deploys via `docker save | ctr import` + `helm upgrade` The remote deploy path (`nav cluster admin deploy --remote`) is completely unaffected — the push logic only activates for local deploys with the env var set. ## Test Plan - `mise run cluster` — end-to-end success, cluster healthy with local images (~168s) - `mise run cluster:deploy` — iterative deploy success, helm upgrade + rollout (~43s) - `mise run pre-commit` — all checks pass (fmt, clippy, 82 tests, python lint) - Verified images present in containerd: `ctr -a /run/k3s/containerd/containerd.sock images ls | grep navigator/` - Remote path verified safe via code analysis (guards prevent push logic from running)
Navigator 🗺️
Navigator is the runtime environment for autonomous agents—the "Matrix" where they live, work, and verify.
While coding tools like Claude help agents write logic, Navigator provides the infrastructure to run it, offering a programmable factory where agents can spin up physics simulations to master tasks, generate synthetic data to fix edge cases, and safely iterate through thousands of failures in isolated sandboxes.
It transforms the data center from a static deployment target into a continuous verification engine, allowing agents to autonomously build and operate complex systems—from physical robotics to self-healing infrastructure—without needing a human to manage the infrastructure.
Quickstart
🚧 Under construction 🚧
uv pip install navigator --index-url https://urm.nvidia.com/artifactory/api/pypi/nv-shared-pypi/simple
navigator sandbox create -- claude # or opencode or codex
The sandbox container includes a minimal networking toolset by default: ping, dig, nslookup, nc, traceroute, and netstat.
Developing
See CONTRIBUTING.md for more information about developing and contributing to Navigator.
Architecture
See architecture/ for detailed architecture docs and design decisions.