mirror of
https://github.com/agent-substrate/substrate.git
synced 2026-10-02 03:24:42 +08:00
Anna PendletonandAnna Pendleton
23863bea16
Cherry-picking #1964 Without it, a pre-built install of v0.2.x (`ate-setup deploy --image-repo --image-tag`) fails on the default envoy router: ate-setup builds envoy-dataplane with docker buildx and has no registry to push to. This brings the fix to release-0.2, along with `make build-envoy-dataplane` and `make build-release-images`, so a 0.2 release can publish the full image set. Only #1964's changes are included: the same 9 files and an identical diff, nothing else from main. Related: #1962 - [x] #1964 merged into main - [x] Tests pass - [x] Appropriate changes to documentation are included in the PR Co-authored-by: Anna Pendleton <13793293+annapendleton@users.noreply.github.com>
ate-setup
Installs and tears down Agent Substrate on a Kubernetes cluster.
go run ./cmd/ate-setup [global flags] <command> [flags]
make build-ate-setup # builds bin/ate-setup
ate-setup is the installer. hack/install-ate.sh is a shim over it, kept so
that existing command lines and CI jobs keep working; it holds no install logic
of its own.
Installing a release
By default every image is built from the checkout with ko, which is what a
developer wants and what the shell installer always did. To install published
images instead, name the registry they were pushed to:
ate-setup deploy ate-system \
--image-repo registry.example.com/substrate \
--image-tag v0.0.0
Nothing is built and no registry is pushed to; the manifests still come from the checkout. Each reference is pinned to the digest its tag names, so the registry has to be readable from here as well as from the cluster.
commands.md— every command with itshack/install-ate.shequivalent.differences.md— where the Go port deliberately behaves differently from the shell scripts it replaced, and what was reproduced exactly.cli-diff.md— what ahack/install-ate.shuser can observe after the switch.