Repository navigation
charts: set the egress credential cache TTL per extra provider - #170
Merged
Merged
Conversation
codyhartsook
marked this pull request as ready for review
November 11, 2026 20:15
The egress gateway reuses a fetched credential for 5 minutes, and a cache hit never reaches the provider. A grant the provider revokes keeps working until the entry expires. agentgateway/agentgateway#4170 added a per-provider cacheTtl, so pass it through atenetEgress.extraCredentialProviders. Entries with unknown keys now fail the render. Before, the chart dropped a misspelled cacheTtl and the 5m cache stayed on. Signed-off-by: Cody Hartsook <cody.hartsook@solo.io>
codyhartsook
force-pushed
the
codyhartsook/cacheTtl
branch
from
November 13, 2026 19:17
413cbce to
968ff36
Compare
shashankram
approved these changes
Nov 13, 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
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.
Some credential providers hand out a user's token only while the actor is handling that user's request. The egress gateway caches each fetched credential for 5 minutes, and a cache hit never reaches the provider. So after the request ends, the actor can keep calling the upstream as that user for up to 5 minutes. A grant the provider revokes lags the same way.
agentgateway/agentgateway#4170 added a per-provider
cacheTtl, and the pinned v1.7.0 image has it. This PR exposes it onatenetEgress.extraCredentialProviders:0ssends every request to the provider.cacheTTLfails at render time.extraCredentialProvidershasn't shipped in a release, so no existing values break.The bundled
k8s.ioprovider andate-setupkeep the default.ate-setupalso drives the Envoy dataplane, which doesn't cache.AI use: AI-assisted. I reviewed the change, ran
helm unittest charts/substrate, and loaded the rendered config withagentgateway --validate-onlyon the pinned image.