fix: Helm-installed atelet cannot prewarm sandbox assets - #33
Merged
Conversation
Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>
supreme-gg-gg
force-pushed
the
jetc/fix/atelet-sa-sandboxconfig
branch
from
September 8, 2026 03:55
f8dbdd0 to
f9743c4
Compare
EItanya
approved these changes
Sep 8, 2026
This was referenced Sep 10, 2026
teemow
added a commit
to giantswarm/agent-platform
that referenced
this pull request
Sep 10, 2026
…Giant Swarm line (#347) * fix(kagent): the dev channel's Substrate worker image comes from the 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. * test(ats): the smoke clears the dev-channel semverFilter where it pins 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.
teemow
added a commit
to giantswarm/agentlab
that referenced
this pull request
Sep 10, 2026
…/giantswarm/substrate) (#144) The lab's Substrate — charts and images — comes from giantswarm/substrate, branch giantswarm: the upstream release the dev channel's kagent pins in its go.mod (kagent-dev/substrate v0.0.26) plus the cherry-picked kagent-dev/substrate#33, published by the fork as multi-arch images and charts under ghcr.io/giantswarm/substrate with dev versions <next upstream patch>-dev.giantswarm.<date>.<time>.h<sha7>. The pinned version is 0.0.27-dev.giantswarm.2026-09-10.19-33-37.h734ec53; the fork tags images with the bare version, so the preloaded worker image drops the v prefix. docs/platform.md and the config comments name the line; the CA/JWT bootstrap port is unchanged.
This was referenced Sep 10, 2026
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
2 participants
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.
Upstream added a feature for sandbox asset prewarming in
atelet. Our chart, however, was not updated to include the permission forateletservice account to read cluster-scopedsandboxconfigs.ate.devresources.Observed atelet log:
The same permission was added to install manifests upstream:
substrate/manifests/ate-install/atelet.yaml
Lines 34 to 38 in f044fd3