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.
As of September 2025, Kong Gateway Enterprise 3.8 will enter its End Of Life (EOL) phase and will no longer be fully supported by Kong. Following this, Kong Gateway Enterprise 3.8 will enter a 12-month sunset support period, focused on helping cus
We're very excited to announce Kong Mesh 2.12 to the world! Kong Mesh 2.12 delivers two very important features: SPIFFE / SPIRE support, which provides enterprise-class workload identity and trust models for your mesh, as well as a consistent Kuma R
Meet Emily. She’s an API product manager at ACME, Inc., an ecommerce company that runs on dozens of APIs. One morning, her team lead asks a simple question: “Who’s our top API consumer, and which of your APIs are causing the most issues right now?”
Today, we’re announcing that Kong has acquired OpenMeter , the open source and SaaS leader for real-time usage metering and billing. OpenMeter’s capabilities will be integrated into Kong Konnect, enabling usage-based pricing, entitlements, and invo
It’s been almost a year since we released our Konnect Terraform provider . In that time we’ve seen over 300,000 installs, have 1.7 times as many resources available, and have expanded the provider to include data sources to enable federated managem
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 Ingre
Update Includes Data Orchestration, CyberArk Support, Solace Integration, and Kafka Schema Validation We’re excited to bring you Kong Gateway Enterprise 3.11 with compelling new features to make your APIs and event streams even more powerful, includ