chore(deps): update gsoci.azurecr.io/giantswarm/agentgateway docker tag to v1.4.1 - #216
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update gsoci.azurecr.io/giantswarm/agentgateway docker tag to v1.4.1#216renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/gsoci.azurecr.io-giantswarm-agentgateway-1.x
branch
from
July 29, 2026 08:31
1c96bf2 to
b6f1dad
Compare
renovate
Bot
force-pushed
the
renovate/gsoci.azurecr.io-giantswarm-agentgateway-1.x
branch
from
July 30, 2026 08:53
b6f1dad to
a56e902
Compare
renovate
Bot
force-pushed
the
renovate/gsoci.azurecr.io-giantswarm-agentgateway-1.x
branch
from
July 30, 2026 10:42
a56e902 to
24fdfb0
Compare
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
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.
This PR contains the following updates:
v1.3.1→v1.4.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
agentgateway/agentgateway (gsoci.azurecr.io/giantswarm/agentgateway)
v1.4.1Compare Source
🎉 Welcome to the 1.4.1 release of the agentgateway project!
Artifacts
Docker images are available:
cr.agentgateway.dev/agentgateway:v1.4.1cr.agentgateway.dev/controller:v1.4.1Helm charts are available:
cr.agentgateway.dev/charts/agentgateway:v1.4.1cr.agentgateway.dev/charts/agentgateway-crds:v1.4.1cr.agentgateway.dev/charts/agentgateway-standalone:v1.4.1Binaries for
agentgatewayand theagctlCLI are available below.Quick Start
Follow the Kubernetes or Standalone quick start guide to get started!
Agentgateway v1.4.1
This release fixes a few bugs around LLM and MCP, increasing compatibility with the new 07-28-2026 specification.
Upgrade notes
llmandmcplisteners may no longer share a port. To expose both on one port, attach them to the same configured gateway.customprovider name may need to be updated.jwt.rawToken.unredacted()as the subject-token source.MCP improvements
LLM and model handling
objectandmodelfields.Prompt guards
llmRequestCEL variable and add CEL-computed headers through standalone configuration, Kubernetes CRDs, and xDS.Authentication and security
ReferenceGrantpolicy.Configuration and operations
Networking
What's Changed
New Contributors
Full Changelog: agentgateway/agentgateway@v1.4.0...v1.4.1
v1.4.0Compare Source
🎉 Welcome to the 1.4.0 release of the agentgateway project!
This release brings a number of highlight features.
First, we have full support for the new MCP 2026-07-28 protocol, which we have been working with the MCP community to develop over the past year.
Additionally, Enterprise-Managed Authorization (also known as Cross App Access) for MCP has been added, enabling centralized access control for MCP servers.
Along the same authentication line, a flexible and feature-rich OAuth token exchange backend authentication mode has been added, enabling a number of security authentication strategies.
The standalone mode has a number of enhancements: configuration created in the UI can now be stored in the database (
sqlitefor local usage,postgresfor remote or HA setups), avoiding the need for a persistent disk. A newgatewaysconfiguration replaces the low-levelbindsAPI and enables serving LLM, MCP, generic routes, and the UI on the same port; additionally, this enables authentication (such as OIDC) for the UI. A newagentgateway-standaloneHelm chart is available for deploying standalone agentgateway in Kubernetes.The Kubernetes deployment has a new (off by default) experimental
AgentgatewayModelAPI, bringing the standalone LLM experience to Kubernetes.AgentgatewayModelallows serving a number of LLM models under the same gateway, routed based on the model name in the request. This offers a higher level API thanAgentgatewayBackend, simplifying the common configuration cases; the existing API remains available.The release also includes Gateway API v1.6 support, fault injection, richer guardrails, and many other enhancements and bug fixes.
Artifacts
Docker images are available:
cr.agentgateway.dev/agentgateway:v1.4.0cr.agentgateway.dev/controller:v1.4.0Helm charts are available:
cr.agentgateway.dev/charts/agentgateway:v1.4.0cr.agentgateway.dev/charts/agentgateway-crds:v1.4.0cr.agentgateway.dev/charts/agentgateway-standalone:v1.4.0Binaries are available below.
Quick Start
Follow the Kubernetes or Standalone quick start guide to get started.
🔥 Breaking changes
Gateway API v1.6 and TCPRoute v1
Agentgateway now builds against Gateway API v1.6, and the Kubernetes controller uses the
v1version ofTCPRouteinstead ofv1alpha2. Re-apply the Gateway API CRDs that match this release before you upgrade.MCP request-phase guardrail rejections return HTTP 200
When an MCP guardrail rejects a request during the request phase, agentgateway now returns the rejection as an HTTP 200 with a JSON-RPC error body, matching the existing response-phase behavior. Update any clients or tests that expected a non-200 status for request-phase rejections.
For more information, see Kubernetes MCP guardrails and Standalone MCP guardrails.
(Standalone)
auth.locationno longer nestsexpressionThe
auth.locationconfiguration no longer uses a double-nestedexpressionfield. Update any policies that set a custom token location to use the flattened form.musl container images removed
The
musl-based container image variants are no longer published. Switch to the standard (glibc) images.The binary releases are still built with
musl.🔒 Security
Stateful MCP sessions can cross routes and overwrite the authorization policy
This release addresses the security advisory GHSA-mvgg-jvj2-4frq of a
High (8.1)severity impacting MCP authorization.Please see the advisory for details and mitigation steps.
Thank you to Aonan Guan for this report.
Request/Response Body CEL policies
A report was made to us that authorization policies written against the
request.bodyorresponse.bodyCEL variables may result in unexpected behavior due to the truncation behavior of these attributes.This is a security recommendation on the usage of these fields in authorization policies, and not a bug in agentgateway.
This behavior has also changed in this release; see below:
request.bodyhttp.maxBufferSize(default 2MB)request.bodyrequest.truncatedBodyrequest.truncatedBodyhttp.maxBufferSize(default 2MB)The split between
bodyandtruncatedBodyallows more control over the body when it exceeds the maximum buffer size.In all cases, usage of these fields in authorization requests is prone to mistakes. For example, consider this request:
If the request is over 2MB, the
attacker-payloadmay be present but missed.Additionally, request encoding schemes (compression, etc) can result in additional bypasses.
When using these fields in authorization policies, ensure the policy correctly degrades in these cases.
Thank you to Aonan Guan for this report.
🌟 New features
MCP protocol 2026-07-28 support
Agentgateway adds support for the upcoming MCP
2026-07-28protocol version.initializehandshake for modern requests._metafield.Because MCP
2026-07-28support is new in this release, most of it is not yet covered by a dedicated guide. For the fields available today, see the Kubernetes API reference and Standalone configuration reference.Cross App Access for MCP
Agentgateway supports MCP Enterprise-Managed Authorization through the OAuth Identity Assertion Authorization Grant, also known as Cross App Access or ID-JAG. An enterprise identity provider can broker access between a client application and the MCP server without the end user completing a separate OAuth flow for each downstream app.
For more information, see Kubernetes Cross App Access and Standalone Cross App Access.
OAuth token exchange backend authentication
Agentgateway can exchange an incoming token for a backend credential by using RFC 8693 OAuth 2.0 token exchange and the RFC 7523 JWT bearer grant. This release adds Kubernetes controller support, custom token types and OAuth 2.1 exchange defaults, the ability to inject multiple secret-sourced headers, and an override for the resolved secret key.
For more information, see Kubernetes OAuth token exchange and Standalone OAuth token exchange.
New MCP authentication providers
Agentgateway adds native MCP authentication provider support for Microsoft Entra ID. Standalone also adds native providers for Descope and authentik.
The
entraprovider bridges OAuth behaviors that Microsoft Entra ID implements differently from the MCP authorization specification, including serving RFC 8414 metadata from Entra's OIDC discovery document, stripping the RFC 8707resourceparameter, and short-circuiting Dynamic Client Registration with your pre-registered application ID.For more information, see Kubernetes MCP authentication, Standalone MCP authentication, and the Standalone Descope integration guide.
New standalone
gatewaysconfiguration modelStandalone configuration gains a new top-level
gatewaysconcept that unifies the UI, LLM, MCP, and routes so that they can share a single listener and port.gatewayssupersedesbinds; existingbindsconfiguration continues to work, and the UI offers a one-click migration frombindstogateways.This release also adds simpler host and TLS configuration, the ability to serve LLM and MCP traffic on the same port, and an internal bind mode with wildcard fallback. For the full configuration surface, see the Standalone configuration reference.
Virtual keys from ConfigMaps and hashed keys
Virtual keys can now be sourced from a
ConfigMapin addition to aSecret, and API keys can be stored as SHA-256 hashes so that raw key material never needs to live in the cluster or in plaintext configuration.For more information, see Kubernetes virtual keys and Standalone virtual keys.
CEL enhancements
This release expands the CEL surface across policy, telemetry, and transformations:
CONNECTrequest headers throughsource.connectHeaders, and use a CEL replace mode for header transformations.For the full CEL surface, see the Kubernetes CEL reference and Standalone CEL reference.
Fault injection: request delay
A new
delaytraffic policy injects latency before a request is forwarded to the backend, for fault-injection and chaos testing. The delay duration accepts a duration string or a CEL expression that returns a duration, or a number interpreted as milliseconds. Injected delay counts against the request timeout.For more information, see Kubernetes fault injection and Standalone fault injection.
AWS assume-role session tags and session name
AWS
assumeRolebackend authentication supports STS session tags and a configurableRoleSessionName. Both the session name (sessionNameExpression) and per-tag values (tags[].expression) can be set from CEL expressions evaluated per request, so you can propagate identity attributes such asjwt.subinto the assumed AWS session.For more information, see Standalone backend authentication. For Kubernetes fields, see the Kubernetes API reference.
Guardrail enhancements
Guardrails include several new operational and policy controls:
BackendConnectionPolicycontrols the TCP, TLS, HTTP, and tunnel settings agentgateway uses when it calls out to a guardrail service, and is available on the OpenAI moderation, Bedrock guardrails, and Google Model Armor policies.failureModefor external processing: External processing supports fail-open or fail-closed behavior.For more information, see Kubernetes LLM guardrails, Standalone prompt guards, Kubernetes MCP guardrails, and Standalone MCP guardrails.
External processing enhancements
The Kubernetes controller supports
metadataContext,requestAttributes, andresponseAttributesfor external processing, andextProcexposes afailureModefor fail-open or fail-closed behavior.For more information, see Kubernetes external processing and Standalone external processing.
LLM gateway enhancements
generateContentmodel and usage extraction in detect mode.For the list of supported providers, see Kubernetes LLM providers and Standalone LLM providers.
Deployment, operations, and packaging
agentgateway-standaloneHelm chart deploys standalone agentgateway, with support for a metrics service andServiceMonitor. For more information, see Standalone Helm deployment.DaemonSet.extraContainersvalue runs sidecar containers in control plane pods.PodMonitor, and a newagentgateway_controller_build_infometric reports controller build details.For more information, see Kubernetes Helm installation, Kubernetes control plane metrics, and Standalone metrics.
Contributors
Thank you to everyone who contributed code, reviews, documentation, bug reports, and CI improvements for this release!
See the full contributor list below.
What's Changed
kube-api-linterversion and fixgoseclinter by @dongjiang1989 in #2366expressionby @howardjohn in #2411go mod downloadby @johananl in #2446Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.