Repository navigation
[Automated] Draft docs (agentgateway): jwks: validate keys a bit more for status - #1509
Merged
Merged
Conversation
… for status Drafts-Commit: 59a2b67 Signed-off-by: GitHub Action <action@github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Art Berger <art.berger@solo.io>
Signed-off-by: Art Berger <art.berger@solo.io>
artberger
approved these changes
Nov 17, 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.
agentgateway/agentgateway#4291 — jwks: validate keys a bit more for status
Docs versions:
kubernetes/mainWhat changes for users: Kubernetes policies with inline JWKS keys that omit
kidor use symmetricoctkeys now report the invalid key in policy status. The affected provider is still emitted, so operators must check thePartiallyValidreason and condition message.What the docs now say: The Debug your setup page adds inline JWKS invalid-key cases to the
PartiallyValidtroubleshooting table, including the supported asymmetric key types and the recommended remote JWKS production setup.How
agentgateway-4291was draftedPlan, and what changed it
PartiallyValidpolicy status.content/docs/kubernetes/main/documentation/operations/debug.mdalready has aPartiallyValidtable and a remote JWKS row, while the policy overview pages do not troubleshoot status.Why a documentation change is necessary
The pull request adds status validation for inline JWKS keys without
kidand symmetricoctkeys. The debug page already tells operators to diagnose partially accepted policies from status, but its table covered only remote JWKS fetch failures. Without this row, a reader who seesAccepted=Truewithreason: PartiallyValidfor an inline JWKS policy does not have the new status case on the troubleshooting page that owns it.How to verify this change
spec.traffic.jwtAuthentication.providers[].jwks.inlineto{"keys":[{"kty":"oct","kid":"hmac","alg":"HS256","k":"c2VjcmV0"}]}.kubectl get agentgatewaypolicy <name> -n <namespace> -o json | jq -r '.status.ancestors[]?.conditions[]? | select(.type == "Accepted") | "\(.status) \(.reason): \(.message)"'.True PartiallyValidand includesinline JWKS key "hmac" is symmetric (oct); only RSA, EC, and Ed25519 keys are supported.Files in this pull request
content/docs/kubernetes/main/documentation/operations/debug.mdHow the pages were chosen (triage report)
Draft a documentation change
agentgateway/agentgateway#4291 — jwks: validate keys a bit more for status
agentgateway/websiteRelease notes. This change's release note is not in this pull request. agentgateway/website keeps the PR tracker's notes in one pull request, from a
pr-tracker-draft-rolling-notes-*branch, and this run adds it there.Draft branch:
pr-tracker-draft-agentgateway-4291