mirror of https://github.com/agent-substrate/substrate.git synced 2026-11-12 10:35:06 +08:00

Files

T

Haven Xia 2eeee044e6 ate-setup: take the prebuilt version from the tag without its digest (#1400 )

With --image-repo the image tag becomes the substrate version, which
names the atelet DaemonSet and the node label. A tag written with its
digest, v1@sha256:..., is a valid image reference but not a valid label
value, so the install failed at the atelet step unless VERSION was also
set. The version is now the tag alone; the digest still pins the image.

Followup for #1391


- [ ] Tests pass
- [ ] Appropriate changes to documentation are included in the PR

2026-09-02 10:09:20 -07:00

internal

ate-setup: take the prebuilt version from the tag without its digest (#1400 )

2026-09-02 10:09:20 -07:00

commands.md

ate-setup: widen digest-lookup auth and pass through pinned tags (#1391 )

2026-09-02 10:04:23 -07:00

differences.md

ate-setup: add flags and functionality to use pre-built images (#1388 )

2026-09-01 21:49:09 -07:00

main.go

Go-based hack scripts (#1190 )

2026-08-27 15:06:13 -07:00

README.md

ate-setup: add flags and functionality to use pre-built images (#1388 )

2026-09-01 21:49:09 -07:00

README.md

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 a Go port of hack/install-ate.sh and the scripts it sources. Both work today and can be used against the same cluster.

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 its hack/install-ate.sh equivalent.
differences.md — where the port deliberately behaves differently, and what was reproduced exactly.