fix(kagent): the dev channel's Substrate worker image comes from the Giant Swarm line - #347
Merged
Conversation
…Giant Swarm line kagent.substrateWorkerPool.workerImage is ghcr.io/giantswarm/substrate/ateom-gvisor:0.0.27-dev.giantswarm.2026-09-10.19-33-37.h734ec53 — the gVisor worker the fork giantswarm/substrate publishes from its giantswarm branch (upstream kagent-dev/substrate 0.0.26, the version the kagent line's go.mod pins, plus the cherry-picked kagent-dev/substrate#33) instead of upstream's ghcr.io/kagent-dev/substrate/ateom-gvisor:v0.0.26. The fork tags images with the bare version. The README's Substrate prerequisite names the fork's charts: the control plane a cluster runs must be the same version as the worker image.
…s the candidate's exact version On poc/kagent-main the chart's defaults admit only -dev.poc-kagent-main. builds; a pull request's candidate carries its own branch name, so the exact pins of gitops.self and the connectivity component matched no tag and the install timed out on every pull request against the line.
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
1 participant
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.
Dev channel (
poc/kagent-main, the kagent API v2 line):kagent.substrateWorkerPool.workerImageisghcr.io/giantswarm/substrate/ateom-gvisor:0.0.27-dev.giantswarm.2026-09-10.19-33-37.h734ec53— the gVisor worker image the fork giantswarm/substrate publishes from itsgiantswarmbranch (upstream kagent-dev/substrate 0.0.26, the version the kagent line'sgo.modpins, plus the cherry-picked kagent-dev/substrate#33;FORK.mdthere is the ledger) instead of upstream'sghcr.io/kagent-dev/substrate/ateom-gvisor:v0.0.26. The fork tags images with the bare version. Tracking: giantswarm/giantswarm#37757 (epic giantswarm/giantswarm#37705, D3).The Substrate control plane a cluster runs must be the same version as the worker image: the README's Substrate prerequisite now names the fork's charts (
oci://ghcr.io/giantswarm/substrate/helm); agentlab installs the same version (giantswarm/agentlab PR alongside). The render is otherwise unchanged;helm/agent-platform/README.mdcarries the new default.Verification: the branch's ATS smoke runs with kagent off (kind has neither the gates nor Substrate), so this value is proven in agentlab from published artifacts: a fresh isolated lab on
--chart-branch poc/kagent-mainpicks up the dev build this merge publishes,ate-systemruns onlyghcr.io/giantswarm/substrate/*images, theWorkerPoolnames this image, and every proof (platform-test,test,backstage-test,agents-test,toolsets-test,models-test) is green. Merge-then-verify on the dev branch is deliberate: the lab follows the branch's published builds, and the change is one image reference.