At Kong Summit this year, we announced the general availability of Kong Ingress Controller (KIC) 2.6. Today we are excited to announce the release of [KIC 2.7](https://docs.konghq.com/kubernetes-ingress-controller/latest/deployment/overview/)KIC 2.7 with even more features and improvements.
Earlier this year, we launched [KIC 2.2](https://konghq.com/blog/kong-ingress-controller-2-2)KIC 2.2 with initial support for [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/)Kubernetes Gateway API. Since then, we've continued to refine and iterate on our implementation of Kubernetes Gateway API. In KIC 2.7 we've graduated the following APIs `GatewayClass, Gateway and HTTPRoute` to beta. Alpha stage APIs (TCPRoute, UDPRoute, TLSRoute, ReferenceGrant) have been moved behind a different [feature gate](https://docs.konghq.com/kubernetes-ingress-controller/latest/references/feature-gates/)feature gate.
With KIC 2.7, we're graduating a few of our alpha APIs to beta. This means that parts of Kubernetes Gateway API are no longer behind a feature flag and are readily available to use in KIC. The specific APIs are `GatewayClass`, `Gateway` and `HTTPRoute`.
In KIC 2.7, we've moved the following APIs to an `alpha` stage:
As time progresses, we expect the upstream maturity and adoption of these L4 protocols to mature and for these APIs to also advance to beta. For the time being, these can be [enabled by adding](https://docs.konghq.com/kubernetes-ingress-controller/latest/references/feature-gates/)enabled by adding the `–feature-gates=GatewayAlpha=true` to your configuration.
Our Prometheus integration is integral for our customers to understand the health of their ingress controller by supplying metrics around configuration pushes and latency. In KIC 2.7, Prometheus metrics now highlight configuration push failures caused by conflicts. The `ingress_controller_configuration_push_count` Prometheus metric now reports `success=”false”` with a `failure_reason=”conflict|other”` label, distinguishing configuration conflicts from other errors (transient network errors, Kong offline, Kong reported non-conflict error, etc.). With this added visibility, our customers are able to determine why a configuration push may have failed and act accordingly.
Plugins are an important part of the Kong ecosystem. Being able to decide what plugins run in which order is an important use case that can improve efficiency and allow for the custom transformation of a single request.
For example, being able to run the rate-limiting plugin before the authentication plugin will help in dealing with brute force attacks. With KIC 2.7, `KongPlugins` and `KongClusterPlugins` can be adapted to be used in a user defined order.
As the Kubernetes SIG group continues to innovate on the Gateway API, Kong will be there to follow and keep feature parity. More specifically, future Gateway API release will contain the following features:
Accompanying this functionality will also be the launch of our Gateway Operator. At a glance, the Gateway Operator is a tool to automatically provision, configure and upgrade Kong Gateway and KIC, manage multiple deployments of the gateway in a single cluster, and support multiple Gateway instances.
Get started with [KIC 2.7](https://docs.konghq.com/kubernetes-ingress-controller/latest/deployment/overview/)KIC 2.7 today! As always, feedback is welcome. You can keep track of the progress on our [Github repository](https://github.com/Kong/gateway-operator)Github repository.
Kong Ingress Controller 3.1 provides brand-new capabilities for keeping your secrets secure. We’ve introduced new KongVault and KongLicense CRDs, and added a way to keep sensitive information in your cluster when using KIC in Konnect. Finally, t
[](https://konghq.com/blog/product-releases/kic-3-1)
Kubernetes, or K8s, is one of the most powerful open source container orchestration systems — especially for its automatic implementation of a desired state. In other words, as an admin, you get to specify how you want your application and cluster t
[](https://konghq.com/blog/learning-center/kubernetes-controllers-vs-operators)
Simplified controller configuration When using the Kong Ingress Controller, a significant amount of effort was needed to apply configuration to the controller by setting environment variables. The new ControlPlane resource greatly simplifies this an
[](https://konghq.com/blog/product-releases/kong-operator-2-0)
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
[](https://konghq.com/blog/product-releases/kubernetes-experience-in-konnect)
Happy holidays everyone! We've been working hard on the Kong Ingress Controller (KIC) and the latest 3.4 release is jam-packed with new features, bugfixes, and improvements. With this update, we're introducing easier TLS encryption, enhanced perfor
[](https://konghq.com/blog/product-releases/kong-ingress-controller-3-4)
We’ve just shipped Kong Ingress Controller (KIC) 2.10! This release makes KIC easier to use. In this blog we’ll cover: Expression Router: KIC 2.10 provides an early access preview to a new Rust-based router that has been available since Kong Gat
[](https://konghq.com/blog/product-releases/whats-new-in-kong-ingress-controller-2-10)
We're happy to announce the release of Kong Ingress Controller (KIC) 2.9, in which we've taken significant steps towards solution extensibility, deployment flexibility, and lowering the cost of ownership. [iframe loading="lazy" title="What's new in
[](https://konghq.com/blog/product-releases/kong-ingress-controller-2-9)