Repository navigation
What's Changed
Security hardening
- atenet-egress no longer connects to loopback, link-local, unspecified or cloud metadata addresses after it resolves a name. Before this, an actor with a
*http or https rule could reach the metadata server or Envoy's admin port through the gateway, using a hostname, Host header or SNI that resolved to one of those addresses. Denied requests now get a 403 with a body that says why. TLS passthrough closes the connection. (#3881) - Go upgraded to 1.27.4 to fix GO-2026-6859 in
net/http. (#3857) github.com/klauspost/compressupgraded to v1.20.4 to fix GO-2026-6865. (#3850)
Bug fixes
- When an actor takes too long to resume, the router now returns
503 actor <ref> is still resuming, retryinstead of an empty 504. The resume keeps running, and retries join it. Before this, gRPC clients sawUnavailablewith an empty message. (#3361) - The k8s-credential-provider
/statuszpage now shows each grant'ssecretSelector.matchLabels. Before, a grant narrowed by labels looked the same as an unrestricted namespace grant./statusz?format=jsonkeepspolicy_grantsunchanged and addspolicy_grant_details. (#3765) - The k8s credential provider now caches each Secret it reads for
--secret-cache-ttl(default10s,0disables). Before, it read the Secret from the API server once per injected header on every egress request, which used up--kube-api-qpsunder load. Authorization still runs on every fetch. (#3635) - The draft release scripts retry GitHub API calls. (#3704, #3928)
Full Changelog: v1.0.0...v1.0.1
Images
Container images for this release are published as ghcr.io/agent-substrate/substrate/<image>:v1.0.1 for linux/amd64 and linux/arm64. The images a release publishes are listed in Release images.
Install
From a checkout of v1.0.1, with Go, install the release images into the current kubectl context. On GKE, the default --sandbox-classes=gvisor,microvm downloads microVM guest assets from GitHub and uploads them with gcloud to gs://<bucket>-assets (created with atelet read access by tools/setup-gcp create bucket and create iam in https://github.com/ai-on-gke/substrate-gke). Add --kind for a kind cluster, or --sandbox-classes=gvisor to skip microVM staging.
git clone --depth 1 --branch v1.0.1 https://github.com/agent-substrate/substrate.git
cd substrate
go run ./cmd/ate-setup deploy ate-system \
--image-repo ghcr.io/agent-substrate/substrate --image-tag v1.0.1 \
--storage-bucket-name=<bucket> \
--credential-provider='{"name":"k8s.io"}' \
--ingress-allowed-spiffe-ids=<SPIFFE IDs of your ingress clients>See Installing pre-built images for the flags.
kubectl-ate
kubectl-ate is attached for Linux and macOS on amd64 and arm64. Download the binary for your platform and its .sha256 file, check it, and put it on your PATH as kubectl-ate:
shasum -a 256 -c kubectl-ate-linux-amd64.sha256
install -m 0755 kubectl-ate-linux-amd64 ~/.local/bin/kubectl-ate