Repository navigation
feat(chart): render an api.kagent.dev/v1alpha3 Agent - #56
Merged
Merged
Conversation
QuentinBisson
force-pushed
the
chore/kagent-v1alpha3-20261005
branch
from
October 6, 2026 09:33
a02479a to
33a0694
Compare
Published Helm chart
|
| Chart | agent |
| Version | 1.5.4-r7fb489f8t20261008092610h79aafbf |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent:1.5.4-r7fb489f8t20261008092610h79aafbf |
| Digest | sha256:65e3ac72cddacaf0bad7a4464186a0dc92286e3e8598c31a6d3a8b9e04c03164 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent --version 1.5.4-r7fb489f8t20261008092610h79aafbfPosted by architect-orb · build 641 · commit 79aafbf · updated in place on every push
…te inline and the Harness by name
One Agent named after the release carries everything the AgentTemplate
carried under spec.template and names the platform Harness in
spec.harnessRef (agent.harness, default kagent); the admission label is gone
with Harness.spec.allowedAgentTemplates. The muster RemoteMCPServer moves to
the new group. New value plugins[] (immutable source plus the skills to
enable, plugin.schema.json mirrors skill.schema.json); sub-agent bindings
under extraTools are {subAgent: ...}. No agent.limits: the API has no
spec.template.limits, turn limits are Harness.spec.claude.limits. The render
suite is agent_test with a new golden snapshot; the ATS reads readiness from
the Agent's status and applies the api.kagent.dev CRDs.
The CRD URLs, the kagent and substrate chart versions, the ateom-gvisor worker image and the Go ADK runtime image digest all move to the two releases; 1.2.4's Go ADK image crashed the golden boot on the 1.4.0 worker (mkdir /config: permission denied), since the /config directory for its own user came with 1.3.0.
…e release-owned gVisor worker
QuentinBisson
force-pushed
the
chore/kagent-v1alpha3-20261005
branch
from
October 8, 2026 09:26
409e016 to
79aafbf
Compare
QuentinBisson
marked this pull request as ready for review
October 8, 2026 10:06
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.
Problem
The kagent line moves to
api.kagent.dev/v1alpha3, where an agent is anAgent(template inline or by reference, Harness by name) and the Harness no longer admits templates through a selector. The chart still renders akagent.dev/v1alpha3 AgentTemplateand an admission label that the new controller never reads, so an agent installed from it would never become Ready on the re-pinned platform.Change
The chart renders one
Agentnamed after the release with the template inline underspec.templateand the platform Harness inspec.harnessRef.name(agent.harness, defaultkagent); the musterRemoteMCPServermoves to the new group. Newplugins[]value (immutable source plus the skills to enable), sub-agent bindings underextraToolsbecome{subAgent: ...}, no admission label is rendered, andagent.egressrendersAgent.spec.egress, the HTTP(S) origins the agent may reach beyond what its revision compiles (kagent-dev/kagent#3019, which the kagent line must carry). The unittest suite and golden snapshot follow, and the ATS reads readiness from the Agent's own status, applies the sixapi.kagent.devCRDs and tests a missing Harness as the fail-fast case. The ATS pins (tag, image digest, CRD URLs) stay at the current line and move to the first giantswarm/kagent-upstream tag that servesapi.kagent.devonce it is published; until then the ATS job cannot pass.