fix: agentgateway controller at the line's 2.0.0 under its nested name - #613
Conversation
Published Helm chart
|
| Chart | agent-platform |
| Version | 3.23.2-dev.fix-agentg--e-images-3x.2026-09-21.05-53-42.hf2bb915 |
| OCI reference | oci://gsoci.azurecr.io/charts/giantswarm/agent-platform:3.23.2-dev.fix-agentg--e-images-3x.2026-09-21.05-53-42.hf2bb915 |
| Digest | sha256:7fc3b73ddda5205d450fe51895f2846fa4cb8c064ad6acc94ff17ea4fa546e99 |
| Registry | public — gsoci.azurecr.io |
| Git catalog | giantswarm-test-catalog (index) |
Pull this chart
helm pull oci://gsoci.azurecr.io/charts/giantswarm/agent-platform --version 3.23.2-dev.fix-agentg--e-images-3x.2026-09-21.05-53-42.hf2bb915Posted by architect-orb · build 10931 · commit f2bb915 · updated in place on every push
Packaging chart giantswarm/agentgateway 2.3.0 moved its image defaults to
the agentgateway line's nested names (giantswarm/agentgateway-upstream/
{controller,agentgateway}:2.0.0). This chart still overrode
agentgateway.controller.image.repository with the flattened
giantswarm/agentgateway-controller and followed 2.x; a value wins over a
chart default, so the render became agentgateway-controller:2.0.0, a tag
that exists only under the nested name, and every installation on this
line rolled its agentgateway HelmRelease back to 2.2.2 (Ready=False,
RetriesExceeded).
The meta chart now names the line's release in full: controller.image
giantswarm/agentgateway-upstream/controller:2.0.0 and proxy.image
giantswarm/agentgateway-upstream/agentgateway:2.0.0, with
components.agentgateway.versionRange >=2.2.2 <3.0.0 (the first packaging
release that renders a bare tag as written). The block is forwarded to
the connectivity release, whose AgentgatewayParameters render proxy.image
into every data plane, so controller and data planes move together to
2.0.0 -- built from the upstream pin (main@c1d24607) the fleet's
v1.5.1-gs.4 controller already ran; the connectivity chart's defaults
mirror the pin. examples/customer-bom.yaml pins 2.2.2;
verify-agentgateway-wiring asserts the nested names and one bare tag;
verify-modes' golden is origin/release-v3.x (origin/main is the 4.x line)
and renders the data-plane pin on both sides.
The shape main took in #609 (4.49.0).
4bf123e to
f2bb915
Compare
|
Proof on a fresh 3.x lab (agentlab 0.54.4, chart 3.23.1 installed with
Template proof: the forwarded values rendered through packaging chart 2.3.0 give |
|
Rolled out. Tag Follow-up outside this repo: giantswarm/agentlab#236, so the next 3.x fix can be proven with |
1 participant
Problem
Packaging chart giantswarm/agentgateway 2.3.0 moved its image defaults to the agentgateway line's nested names,
gsoci.azurecr.io/giantswarm/agentgateway-upstream/{controller,agentgateway}:2.0.0. The 3.x meta chart still overridesagentgateway.controller.image.repositorywith the flattenedgiantswarm/agentgateway-controllerand follows2.x. A value wins over a chart default, so the render isgsoci.azurecr.io/giantswarm/agentgateway-controller:2.0.0, a tag that exists only under the nested name (ErrImagePull). Every installation on this line has itsagentgatewayHelmRelease atReady=False,Stalled=True RetriesExceeded, rolled back to 2.2.2; a fresh install of the chart fails on that HelmRelease.Solution
The shape
maintook in #609 (4.49.0):agentgateway.controller.imagegiantswarm/agentgateway-upstream/controller:2.0.0,agentgateway.proxy.imagegiantswarm/agentgateway-upstream/agentgateway:2.0.0, so a packaging release cannot move the images.components.agentgateway.versionRangeis>=2.2.2 <3.0.0(was2.x): 2.2.2 is the first packaging release that renders a bareX.Y.Ztag as written.AgentgatewayParametersrenderproxy.imageinto every data plane: controller and data planes move together to 2.0.0, which is built from the upstream pin (main@c1d24607) the fleet'sv1.5.1-gs.4controller already ran. The connectivity chart's defaults mirror the pin.examples/customer-bom.yamlpins2.2.2;tests/verify-agentgateway-wiring.pyasserts the nested names and one bare tag;verify-modes' golden isorigin/release-v3.x(origin/mainis the 4.x line) and renders the data-plane pin on both sides; CHANGELOG, UPGRADE.md, the README tables.Acceptance criteria
make verify-meta verify-components verify-modesgreen.gsoci.azurecr.io/giantswarm/agentgateway-upstream/controller:2.0.0, which exists on gsoci (sha256:19b896b1…).agentgatewayHelmRelease to 2.3.0,Ready=True, the controller onagentgateway-upstream/controller:2.0.0, the data plane onagentgateway-upstream/agentgateway:2.0.0, the platform's identity proofs through the edge green.<4.0.0has itsagentgatewayHelmReleaseReady=Trueonagentgateway@2.3.0.The merge is a rollout to every installation on the 3.x line: the controller and the edge data plane restart onto 2.0.0.