Kong on Ivan Versluis — Networknethttps://networknet.nl/tags/kong/Recent content in Kong on Ivan Versluis — NetworknetHugoenTue, 15 Sep 2026 16:05:17 +0200Building a Kong gateway foundation for APIs, LLMs and MCPhttps://networknet.nl/notes/kong-api-llm-mcp-gateway/Tue, 15 Sep 2026 13:00:00 +0200https://networknet.nl/notes/kong-api-llm-mcp-gateway/<h2 id="from-ingress-controller-to-integration-boundary">From ingress controller to integration boundary</h2> <p>Kong has been part of my Kubernetes homelab for some time. Initially, its role was relatively conventional: terminate TLS, provide ingress and apply policies before traffic reached a workload.</p> <p>That role has changed.</p> <p>As I added LLM integrations, MCP servers and automation around n8n and OpenClaw, I started seeing the same problem from different directions. Each new integration could easily introduce another direct connection, another credential and another piece of application-specific configuration.</p>