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](https://docs.konghq.com/gateway-operator/changelog/)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](https://docs.konghq.com/gateway-operator/1.6.x/guides/konnect-entities/architecture/)manage configuration with KGO, although entities are read-only in Kubernetes. Learn more about this new capability [here](https://docs.konghq.com/gateway-operator/1.6.x/guides/konnect-entities/gatewaycontrolplane/#refer-to-existing-konnect-gateway-control-plane)here.
If you aren’t already using [KGO](https://docs.konghq.com/gateway-operator/latest/)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](https://docs.konghq.com/konnect/gateway-manager/dedicated-cloud-gateways/transit-gateways/)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](https://docs.konghq.com/gateway-operator/1.6.x/guides/konnect-entities/cloud-gateways-transit-gateway/)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](https://docs.konghq.com/gateway-operator/1.6.x/reference/custom-resources/#controlplaneoptions)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](https://docs.konghq.com/gateway-operator/1.6.x/reference/custom-resources/#dataplaneserviceoptions) 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,](https://github.com/kong/gateway-operator) Kong Gateway Operator repository, and help us make KGO even better.
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
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
You invested in Kong Konnect. You centralized your API governance, locked down your routing, enforced your security policies, and gave your organization a single source of truth for every API in your estate. That work is done, and it is working. So
Before we jump into prepaid credits, let’s review the basics. The two terms, tokens and credits, sometimes get used interchangeably in the space, so it’s worth untangling. A token is a unit of data for large language models that can be either co
Until now, KAi could tell you how to set up a service, suggest the right plugins, and point you at the docs. Useful, but you still had to do some of the work yourself. V2 changes that. With our new Code Mode MCP integration, KAi can create, update
Have you ever…. Copied an API spec out of Kong Konnect, or where you manage your APIs, pasted it into your API client, and immediately wondered if it’s the latest version? Sent an email to your platform team with the subject line “ which endpoint sh