Repository navigation
feat(helm): further credential providers for the egress gateway - #90
Open
QuentinBisson wants to merge 1 commit into
Open
QuentinBisson wants to merge 1 commit into
QuentinBisson wants to merge 1 commit into
Conversation
QuentinBisson
marked this pull request as ready for review
October 18, 2026 12:56
QuentinBisson
added a commit
to giantswarm/substrate
that referenced
this pull request
Oct 18, 2026
…he dropped class FORK.md names kagent-dev#90 as the upstream exit of the routing value, which covers the chart only. The upgrade step describes the window in which the bundled provider refuses a Google access-token fetch without claiming a status code or retry. The parser keeps refusing an unknown k8s.io subdomain and now refuses google-access-token.k8s.io explicitly.
QuentinBisson
added a commit
to giantswarm/substrate
that referenced
this pull request
Oct 18, 2026
…he dropped class FORK.md names kagent-dev#90 as the upstream exit of the routing value, which covers the chart only. The upgrade step describes the window in which the bundled provider refuses a Google access-token fetch without claiming a status code or retry. The parser keeps refusing an unknown k8s.io subdomain and now refuses google-access-token.k8s.io explicitly.
This was referenced Oct 18, 2026
Open
The egress gateway already selects a credential provider by URI authority, but the chart rendered the bundled k8s.io provider only. The value credentialProvider.additionalProviders adds providers beside it on both the HTTPS and the HTTP listener, each dialed with the gateway's pod identity and verified against the servicedns.podcert.ate.dev trust bundle. An entry needs a lowercase DNS name as uriAuthority and <service>.<namespace>.svc:<port> as host, cannot replace k8s.io and cannot repeat an authority. The default render is unchanged. Signed-off-by: QuentinBisson <quentin@giantswarm.io>
QuentinBisson
force-pushed
the
feat/egress-credential-providers
branch
from
October 26, 2026 13:15
6f1241f to
9a4ce16
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.
Problem
The egress gateway already selects a credential provider by the
ate-secret://URI authority (credentialProvidersis a list), but the chart renders the bundledk8s.ioprovider only. An installation that keepsk8s.iofor API keys cannot add a provider of its own beside it, such as one that resolves a caller's credential or exchanges a service account key for a short-lived token, without patching the template.Change
credentialProvider.additionalProvidersadds entries (uriAuthority,hostas<service>.<namespace>.svc:<port>) to both egress listeners next tok8s.io, dialed with the gateway's pod identity and verified against theservicedns.podcert.ate.devtrust bundle. Entries are validated: a lowercase DNS name, no replacingk8s.io, no repeated authority. The default render is unchanged; ahelm unittestsuite covers the entries and the refusals.