Skip to content

fix(ci): move the agentgateway-image parameter to 2.2.2 with the chart - #113

Merged
teemow merged 1 commit into
giantswarmfrom
agw-2.2.2-ci
Oct 2, 2026
Merged

teemow merged 1 commit into
giantswarmfrom
agw-2.2.2-ci

Conversation

@teemow

@teemow teemow commented Oct 2, 2026

Copy link
Copy Markdown
Member

Follow-up to #111, for #109.

Problem

#111 moved the chart default images.agentgateway to 2.2.2 but did not move the agentgateway-image parameter in .circleci/config.yml. The publish job checks that the two are equal, so the tag pipeline of v1.3.1-rc.5 failed at publish/charts with "images.agentgateway differs from the agentgateway-image parameter". The images were published; the charts were not.

Change

  • .circleci/config.yml: agentgateway-image goes to gsoci.azurecr.io/giantswarm/agentgateway-upstream/agentgateway:2.2.2, the same value as the chart default.
  • FORK.md: the "agentgateway it runs" row names 2.2.2 (tag v2.2.2 on 149d9b40). That is 2.2.1 plus agentgateway-upstream#35, which makes an unreachable policy service a 503, minus the named MCP buffer error that agentgateway-upstream#36 reverted.

The open #104, #106, #107 and #108 also edit FORK.md, but only the section near line 73. This PR changes only the row on line 31, so they do not overlap.

Verification

This PR's tag pipeline publishes both charts, and the resulting RC is checked end to end in a test cluster.

This PR was written by an agent.

@teemow
teemow requested a review from a team as a code owner October 2, 2026 08:49
@teemow
teemow merged commit 9cb6698 into giantswarm Oct 2, 2026
14 checks passed
@teemow
teemow deleted the agw-2.2.2-ci branch October 2, 2026 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant