Kong Operator 2.2 and Kubernetes-native control of API platforms

TL;DR: Governance, auditability, and change control now extend deeper into API and eventing operations rather than sitting beside them as Kong Operator 2.2 moves Event Gateway, Dev Portal, Gateway API 1.5.1, and more infrastructure settings into Kubernetes-managed workflows, giving platform teams a more declarative operating model, according to Kong.

NHIMG editorial — what this means for NHI practitioners

Questions worth separating out

Q: How should platform teams govern Kubernetes-native API gateway resources?

A: Treat gateway resources as controlled platform state, not ad hoc runtime configuration.

Q: Why do declarative operators improve platform governance?

A: Declarative operators make the desired state explicit, which helps teams compare what should exist with what is actually deployed.

Q: What breaks when infrastructure labels and annotations are unmanaged?

A: Ownership, policy enforcement, and automation all become inconsistent when labels and annotations are missing or ad hoc.

Practitioner guidance

• Standardise Kubernetes as the source of truth Move Kong gateway, portal, and eventing configuration into the same reviewed Kubernetes workflows you use for other platform resources.
• Apply mandatory metadata controls Define required labels and Service annotations for ownership, environment, cost centre, and observability integration.
• Map traffic exposure to Gateway API resources Document which Gateway API objects control listener policy, TLS routing, and backend exposure for each environment.

What's in the full announcement

Kong's full product release covers the implementation detail this post intentionally leaves for the source:

• Exact resource types added for Event Gateway and Dev Portal management inside the operator
• Release-specific upgrade notes and configuration examples for Gateway API 1.5.1 and TLSRoute
• Operator-level workflow details for Konnect integration and cross-namespace references
• The practical release documentation for teams planning a production rollout

👉 Read Kong's release notes for Kong Operator 2.2 and Kubernetes-native platform control →

Kong Operator 2.2 and Kubernetes-native control of API platforms?

Explore further

View Full Forum →  |  NHI Foundation Course →