We're continuing our efforts to make Kong Gateway Operator (KGO) the preferred way to install, upgrade, scale, and manage a Kong Gateway or Kubernetes Ingress — whether you’re managing from Kong Konnect or Kubernetes. With this latest release, we're:
As ever, we’re continuously addressing issues raised by the community. You’ll find the complete list of improvements in the KGO changelog .
Let’s dig into some of the more important changes to see how they can benefit your Kong Gateway deployment.
Previously, if you wanted to use KGO with Konnect, you had to define the Konnect control plane using KGO and configure it from there. If you have existing Konnect-managed Gateways with existing entities configured, this made it difficult to adopt KGO.
You can now reference existing Konnect control planes in your KGO setup using an existing KonnectID and setting KongGatewayControlPlane to type mirror. You can manage configuration directly in Konnect and also manage configuration with KGO, although entities are read-only in Kubernetes. Learn more about this new capability here.
If you aren’t already using KGO as your management tool of choice for Kong Gateway, maybe it’s time to take a look.
Dedicated Cloud Gateways (DCGW) are Kong Gateways that are fully managed by Kong in the cloud and region of your choice, connected into your cloud VPC network. Transit Gateways in AWS simplify cloud networking by centralizing routing through a central hub, reducing the need for multiple point-to-point peering connections.
Konnect already supports Transit Gateways in AWS for hosted Kong Gateways, and this is a common deployment pattern for Dedicated Cloud Gateways in AWS. KGO now supports this configuration option through the KonnectCloudGatewayTransitGateway entity.
Limiting the Kubernetes namespaces KGO watches is important for resource efficiency and security in shared cluster environments. By configuring the spec.WatchNamespace setting in the ControlPlane and GatewayConfiguration CRDs , you can restrict KGO's synchronization of routes and service configurations to only the designated namespaces relevant to your Kong Gateway deployment. This focused approach prevents unnecessary processing and potential exposure of configurations across different teams or applications within the same cluster. You can learn more about this here.
When you're developing new applications, you may not have full access to the networking setup that you have in higher environments. With this change, you can configure your Kong Gateway DataPlane as a NodePort service in addition to ClusterIP and LoadBalancer configurations, which are already supported. This should make it easier for developers to build solutions using Kong Gateway and KGO.
Kong Gateway Operator 1.6 focuses on delivering practical improvements, especially for customers leveraging Konnect and AWS Transit Gateways.
Try out the new features and give us feedback by visiting the Kong community forums or opening an issue in the Kong Gateway Operator repository, and help us make KGO even better.
A quick refresher: Kong Cloud Gateways Kong Cloud Gateways are fully managed, high-performance data planes running on customer-dedicated infrastructure, orchestrated and operated by Kong through Kong Konnect . Customers can choose between: Serverle
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
Kong Gateway Operator (KGO) is the most effective way to install, upgrade, scale, and manage a Kong Gateway or Kubernetes Ingress. The latest release of the Kong Gateway Operator brings several updates that streamline integration with Kong Konnect
It’s here! The Kong Gateway Operator release we teased at API Summit is now available for you all to use. KGO 1.4 allows you to configure Kong Konnect using CRDs, attach your DataPlane resources to Konnect with minimal configuration, and even ma
We've talked about why 2026 is the year of AI unit economics . There, we explored the "2025 hangover" where organizations realized that without financial governance, AI isn't just a science project but has become a margin-bleeding cost center. But
If you've used KAi before, you'll notice the difference immediately. The enhanced version has deeper access to your Konnect environment and new tools for debugging, analytics, and configuration management: Active tracing and debugging: KAi can now
Every January, the same resolutions show up: eat better, exercise more, finally learn that language, finally figure out that production use case for AI agents (OK, this one isn’t so typical unless you operate in our universe). But if you're respons