Repository navigation
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
Summary
Documents the new
config.certificatesandconfig.ca_certificatesfields on AI MCP Servers and AI Agents (Aha! AI-223, 2.3 GA). Platform API change: Kong/platform-api#3670 (fields gated to minimum runtime version 2.3).app/_ai_gateway_entities/ai-mcp-server.md: new## Upstream TLSsection with{% new_in 2.3 %}— field table, by-name semantics,maxItems: 1and private-key requirement oncertificates, default trust store behavior forca_certificates, YAML example, cross-links to the AI Certificate / AI CA Certificate entities, and a new FAQ. Notes the fields apply to every mode that proxies to an upstream (conversion-only,conversion-listener,passthrough-listener,upstream-server) and not tolistenermode, which has no upstream of its own.app/_ai_gateway_entities/ai-agent.md: same treatment for agent upstreams (a2aandhttptypes).app/_ai_gateway_entities/ai-certificate.md/ai-ca-certificate.md:related_resourcesand FAQ cross-references noting consumption by MCP Servers and Agents for upstream TLS.Note: the
{% entity_schema %}tables render the new fields automatically once the updated Konnect AI Gateway OAS syncs intoapi-specs/from platform-api; no spec edits in this PR.Validation
make validate-frontmatters).Drafted via the AI-223 roadmap pipeline.