Repository navigation
release-0.2: Publish and pin envoy-dataplane for pre-built installs - #1990
Merged
Lior Lieberman (LiorLieberman) merged 1 commit intoSep 30, 2026
Conversation
envoy-dataplane is built from a Dockerfile, not with ko. ate-setup always built it with docker buildx, even for `deploy --image-repo --image-tag`, which has no registry to push to, so a pre-built install failed on the default envoy router after applying the control plane. A pre-built install now pins REPO/envoy-dataplane:TAG like the ko images. To publish it, `make build-envoy-dataplane` builds the image, and `make build-release-images` builds every image a pre-built install needs (ko images, demos, envoy-dataplane), all tagged $(VERSION). The ko tag goes in a new KO_TAGS variable so a KO_FLAGS override doesn't drop it.
Steven Shriver (stshrive)
approved these changes
Sep 29, 2026
Maya Wang (mayawang)
added
area/dev-infra
kind/feature
Lior Lieberman (LiorLieberman)
approved these changes
Sep 30, 2026
Lior Lieberman (LiorLieberman)
merged commit Sep 30, 2026
23863be
into
agent-substrate:release-0.2
5 checks passed
Aditya Shantanu (aditya-shantanu)
pushed a commit
to ai-on-gke/substrate-gke
that referenced
this pull request
Sep 30, 2026
* Default to the v0.2.0-gke.0 release Move the pre-built defaults from v0.1.0-gke.1 to v0.2.0-gke.0 and pin Commit to the head of upstream's release-0.2 branch (23863bea), which is v0.2.0 plus the envoy-dataplane pin pre-built installs need (agent-substrate/substrate#1990). MinGoVersion is unchanged: go.mod at that commit still says go 1.27.0. * Update the demo next steps for release-0.2 At the new pin, kubectl-ate's create actor takes --template rather than --template-ref, and atenet's router picks the actor from an ate-target-actor: <atespace>/<actor> header instead of the Host, so the old curl gets 404 invalid actor reference. Print the commands that work at that revision and update the tests that pin them. * Regenerate the completion screenshot for v0.2.0-gke.0 --------- Co-authored-by: Anna Pendleton <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 withmake build-envoy-dataplaneandmake 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