Skip to content

[Automated] Draft docs (agentgateway): jwks: validate keys a bit more for status - #1509

Merged
artberger merged 4 commits into
mainfrom
pr-tracker-draft-agentgateway-4291
Nov 17, 2026
Merged

artberger merged 4 commits into
mainfrom
pr-tracker-draft-agentgateway-4291

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

agentgateway/agentgateway#4291 — jwks: validate keys a bit more for status

Docs versions: kubernetes/main

What changes for users: Kubernetes policies with inline JWKS keys that omit kid or use symmetric oct keys now report the invalid key in policy status. The affected provider is still emitted, so operators must check the PartiallyValid reason and condition message.

What the docs now say: The Debug your setup page adds inline JWKS invalid-key cases to the PartiallyValid troubleshooting table, including the supported asymmetric key types and the recommended remote JWKS production setup.

How agentgateway-4291 was drafted

Plan, and what changed it

  • Planned: Add the new inline JWKS status cases to the page that already explains PartiallyValid policy status.
  • Learned: content/docs/kubernetes/main/documentation/operations/debug.md already has a PartiallyValid table and a remote JWKS row, while the policy overview pages do not troubleshoot status.
  • Did: Added one inline JWKS row to the debug page and wrote a Security release-note bullet.

Why a documentation change is necessary

The pull request adds status validation for inline JWKS keys without kid and symmetric oct keys. 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 sees Accepted=True with reason: PartiallyValid for an inline JWKS policy does not have the new status case on the troubleshooting page that owns it.

How to verify this change

  1. In a Kubernetes test cluster with agentgateway installed, apply an AgentgatewayPolicy that sets spec.traffic.jwtAuthentication.providers[].jwks.inline to {"keys":[{"kty":"oct","kid":"hmac","alg":"HS256","k":"c2VjcmV0"}]}.
  2. Run kubectl get agentgatewaypolicy <name> -n <namespace> -o json | jq -r '.status.ancestors[]?.conditions[]? | select(.type == "Accepted") | "\(.status) \(.reason): \(.message)"'.
  3. The output shows True PartiallyValid and includes inline 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.md
How the pages were chosen (triage report)

Draft a documentation change

agentgateway/agentgateway#4291 — jwks: validate keys a bit more for status

  • Product: agentgateway (upstream) → agentgateway/website
  • Docs version: kubernetes/main
  • Summary (the title; the body has no description): jwks: validate keys a bit more for status
  • Not tested: no cluster was available, so every command in this diff is unrun

Release 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

… for status

Drafts-Commit: 59a2b67
Signed-off-by: GitHub Action <action@github.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Deploying agentproxy with  Cloudflare Pages  Cloudflare Pages

Latest commit: 243f669
Status:⚡️  Build in progress...

View logs

artberger and others added 2 commits November 16, 2026 20:24
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
artberger merged commit 7319ed8 into main Nov 17, 2026
3 of 5 checks passed
@artberger
artberger deleted the pr-tracker-draft-agentgateway-4291 branch November 17, 2026 01:37
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.

2 participants