We're happy to announce the 3.5 release of Kong Ingress Controller (KIC). This release includes the graduation of combined services to General Availability, support for connection draining, as well as the start of deprecating support for some Ingress types as we help move customers to the Kubernetes Gateway API. Let’s get into more details about these!
Using Combined HTTP Routes, Kong Ingress Controller can now consolidate rules from multiple HTTPRoute resources when they are targeting the same backend services. The default behavior is to create a new Gateway service for each HTTPRoute. For large numbers of HTTPRoutes, this results in added complexity and resource utilization. Enabling this feature can dramatically reduce the number of Kong Gateway services that have to be managed.
The feature is not enabled by default, as it does change the way we name services, but you can enable it by passing the --combined-services-from-different-httproutes flag to the KIC instance or set CONTROLLER_COMBINED_SERVICES_FROM_DIFFERENT_HTTPROUTES=true in the env section of the Helm values.
When Pods in your backing services are in the Terminating phase, Kong Gateway will stop connections to the Pod. In most situations, especially with stateless connections, this is not an issue as another Pod will be able to handle the connection. For session-based workloads and in combination with Sticky Sessions, you may need the connection tear down to happen gracefully.
With the introduction of Connection Draining, your clients will continue to be routed to the same backend Pod until it reaches the terminated phase, allowing your service to gracefully handle in-flight transactions, as well as notifying your clients that their session is coming to an end.
As connection draining is tied to the lifecycle phases of your Pods, you can rely on everything that makes life easier in Kubernetes, including lifecycle hooks, signalling for graceful shutdown, and now all integrated into the Kubernetes Controller and Kong Gateway.
To enable connection draining, pass --enable-drain-support flag to the KIC instance or set CONTROLLER_ENABLE_DRAIN_SUPPORT=true xxx in the env section of the Helm values.
You can then use drain support in combination with sticky sessions:
apiVersion: configuration.konghq.com/v1beta1
kind: KongUpstreamPolicy
metadata:
name: echo-drain-policy
spec:
# Use consistent hashing algorithm for session persistence
algorithm: sticky-sessions
slots: 100
# Configure session-based sticky routing using cookies
hashOn:
cookie: session-id # Name of the session cookie
cookiePath: / # Path for the session cookie
As our customers and the Kubernetes community move towards the stable Gateway API, we have marked KongIngress, TCPIngress, and UDPIngress as deprecated in this release of KIC. You can still use these definitions, but you will see deprecation warnings.
We have migration guides for KongIngress to move to KongUpstreamPolicy, as well as moving from TCP and UDP Ingress to TCPRoute and UDPRoute in the Gateway API.
As always, the quickest way to get started with KIC is with Kong Konnect, thanks to our KIC in Kong Konnect functionality.
Please also share any feedback that you might have on our GitHub discussion forum for KIC here.
Simplify operations and scale with confidence To unlock Kubernetes’ full potential, many enterprises are relying on three key building blocks available in Kong Konnect today: Kubernetes Ingress Controllers: Ingress controllers are used for managing
Happy holidays everyone! We've been working hard on the Kong Ingress Controller (KIC) and the latest 3.4 release is jam-packed with new features, bugfixes, and improvements. With this update, we're introducing easier TLS encryption, enhanced perfor
Kong Ingress Controller (KIC) 3.2 is here, and it’s an incredible release. It contains features related to graph theory, features that mean you’ll never need a database again, and a whole host of quality-of-life fixes. Isolate configuration issues w
As we continue to push the boundaries of API management, we're excited to announce the beta release of Kong Ingress Controller within Kong Konnect. Revealed at KubeCon + CloudNativeCon Europe 2023, this new integration turns Kong Konnect into the wo
Managed Redis cache is a turnkey "Shared State" add-on for Kong Dedicated Cloud Gateways. It is designed to combine the performance of an in-memory data store with the simplicity of a SaaS product. When you spin up a Dedicated Cloud Gateway in Kong
With Kong Ingress Controller, when your Control Plane was hosted in Kong Konnect, and you were using Kubernetes Gateway API, your dataplane, routes, and services were in read-only mode. When using Kong Ingress Controller with Kubernetes Gateway API
The Kong MCP Registry acts as a central directory for AI agents and clients to access services that provide context or take action. For AI agents, think of it as a combination of a "Service Catalog" and a "Developer Portal." It offers the metadata,