## 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 how external traffic enters the Kubernetes cluster, ensuring that APIs and services are exposed securely, reliably, and in a way that scales. Ingress controllers essentially serve as the front door to Kubernetes workloads, managing how external requests are admitted and routed to the right services inside the cluster.
• - **Kubernetes Operators**: Operators take on the operational heavy lifting by automating day-2 tasks such as scaling, upgrades, and certificate rotation. Instead of requiring platform teams to watch over every service manually, Kubernetes operators monitor the cluster and can act automatically to keep things running smoothly.
• - **The Kubernetes Gateway API**: A vendor-neutral standard that modernizes how teams configure traffic routing, policies, and infrastructure within Kubernetes. [The Gateway API](https://gateway-api.sigs.k8s.io/)The Gateway API improves flexibility, separates developer and infrastructure concerns, and makes it easier to switch providers without rewriting configurations.

Together, these components extend Kubernetes from being just a container orchestration platform. They lay the foundation for Kubernetes to support the exposure, governance, and operation of APIs — and the AI workflows that increasingly rely on those APIs.

[*Register for API Summit 2025 today*](https://konghq.com/events/conferences/api-summit?utm_medium=blog&utm_source=reason-2&utm_campaign=api-summit)*Register for API Summit 2025 today**!*

## Kong’s role in simplifying Kubernetes

Kong builds on top of these components to make Kubernetes simpler, more effective, and enterprise-ready. For many years, the Kong Ingress Controller (KIC) simplified traffic routing into Kubernetes clusters, while the Kong Gateway Operator (KGO) automated day-2 operations like autoscaling and certificate rotation. Each solved important but distinct challenges.

Recently, Kong introduced [Kong Operator (KO) 2.0](https://konghq.com/blog/product-release/kong-operator-2-0)Kong Operator (KO) 2.0, marking the first stage of unification between KIC and KGO. The goal of KO 2.0 was to deliver a unified experience in a single operator framework — one that preserves flexibility while delivering a more consistent end-user experience.

## Kong Operator 2.1: One ring to rule all Kubernetes deployments 

The upcoming release of Kong Operator 2.1 at API Summit 2025 will be more than just an incremental update — it will represent the next step in unifying Kubernetes operations for Kong customers. Building on KO 2.0’s consolidation of KIC and KGO, this release will introduce several powerful capabilities focused on providing a first-class Kubernetes experience: 

**Gateway API support in hybrid mode**

Customers had to make a choice previously on having full Kubernetes Gateway API support or being able to use the Konnect API ecosystem. With Kong Operator 2.1, we will support both Gateway API and the Konnect control plane — we call this hybrid mode.

KO 2.1 delivers hybrid mode support that enables teams to use the Gateway API as the declarative interface to manage hybrid Kong deployments, whether those data planes are running in Konnect or in self-managed mode. This streamlines the shift from older ingress resources, reduces operational complexity, and ensures traffic management remains consistent across large-scale Kubernetes environments.

Hybrid mode for Kong Gateway provides full integration with our Konnect ecosystem of products. The gateway control plane is managed by Kong, and integrates with the Kong Konnect ecosystem of API products.

**Konnect Debugger support**

Formerly known as Active Tracing, the [Konnect Debugger](https://konghq.com/blog/product-releases/konnect-debugger)Konnect Debugger is now tightly integrated with KO. This enables teams to capture detailed traces and logs for specific Kubernetes services or routes without additional instrumentation. With this integration, troubleshooting becomes faster, mean time to resolution is reduced, and operations teams gain unprecedented visibility into traffic behavior directly within Kubernetes.

**Automatic Service Catalog integration**

Services created inside of Kubernetes can now be automatically cataloged in Konnect’s Service Catalog. This eliminates the manual effort of registering services, ensuring that everything deployed in the cluster is discoverable and available for governance, documentation, and consumption.

**Developer Portal integration**

Once cataloged, services can flow directly into the Developer Portal, where internal and external developers can securely discover and consume them. This self-service model accelerates delivery by reducing dependency on platform teams and makes Kubernetes-hosted APIs part of the broader enterprise ecosystem.

**Deeper Konnect integration**

Beyond any single feature, KO 2.1 strengthens the connection between Kubernetes and the Konnect platform. The result is a unified experience across traffic management, operations, and governance — one that feels native to Kubernetes but operates with enterprise-level guardrails.

## Learn More at API Summit 2025

Kong Operator 2.1 is a major milestone in unifying Kubernetes operations, setting a new standard for how Kubernetes APIs are deployed, governed, and consumed.

Want to see it in action? [Join us at API Summit](https://konghq.com/events/conferences/api-summit?utm_medium=blog&utm_source=reason-2&utm_campaign=api-summit)Join us at API Summit, where Kong will officially unveil KO 2.1 and demonstrate how it can provide a strong foundation for your broader API and AI strategy and check out the session [Building a First-Class Kubernetes Experience in Konnect](https://konghq.com/events/conferences/api-summit/agenda?agendaPath=session/1692800)Building a First-Class Kubernetes Experience in Konnect.

[Register for API Summit today](https://konghq.com/events/conferences/api-summit?utm_medium=blog&utm_source=reason-2&utm_campaign=api-summit)Register for API Summit today!