Skip to content
Kong Summit 2022: Where API Innovation Runs Wild  —Learn More →
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Konnect Cloud
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Kong Konnect Platform

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Request Demo
  • Kong Gateway
  • Konnect Cloud
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Kong Konnect Platform

  • Docs contribution guidelines
  • 2.5.x (latest)
  • 2.4.x
  • 2.3.x
  • 2.2.x
  • 2.1.x
  • 2.0.x
  • 1.3.x
  • 1.2.x
  • 1.1.x
  • 1.0.x
    • FAQ
    • Changelog
    • Architecture
    • Custom Resources
    • Deployment Methods
    • Kong for Kubernetes with Kong Enterprise
    • High-Availability and Scaling
    • Resource Classes
    • Security
    • Ingress Resource API Versions
    • Kong Ingress on Minikube
    • Kong for Kubernetes
    • Kong for Kubernetes Enterprise
    • Kong for Kubernetes with Kong Enterprise
    • Kong Ingress on AKS
    • Kong Ingress on EKS
    • Kong Ingress on GKE
    • Admission Controller
    • Getting Started with KIC
    • Upgrading from previous versions
    • Getting Started using Istio
      • Using the KongPlugin Resource
      • Using the KongIngress Resource
      • Using KongConsumer and KongCredential Resources
      • Using the KongClusterPlugin Resource
      • Using the TCPIngress Resource
      • Using the UDPIngress Resource
    • Using the ACL and JWT Plugins
    • Using cert-manager with Kong
    • Configuring a Fallback Service
    • Using an External Service
    • Configuring HTTPS Redirects for Services
    • Using Redis for Rate Limiting
    • Integrate KIC with Prometheus/Grafana
    • Configuring Circuit-Breaker and Health-Checking
    • Setting up a Custom Plugin
    • Using Ingress with gRPC
    • Setting up Upstream mTLS
    • Exposing a TCP-based Service
    • Exposing a UDP-based Service
    • Using the mTLS Auth Plugin
    • Configuring Custom Entities
    • Using the OpenID Connect Plugin
    • Rewriting Hosts and Paths
    • Preserving Client IP Address
    • Using Gateway API
    • Using Kong with Knative
    • KIC Annotations
    • CLI Arguments
    • Custom Resource Definitions
    • Plugin Compatibility
    • Version Compatibility
    • Troubleshooting
    • Prometheus Metrics

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

On this page
  • Kong
  • Kong Enterprise
  • Kubernetes
  • Istio
Kubernetes Ingress Controller
2.2.x
  • Home
  • Kubernetes Ingress Controller
  • References
You are browsing documentation for an outdated version. See the latest documentation here.

Version Compatibility

Kong’s Ingress Controller is compatible with different flavors of Kong. The following sections detail on compatibility between versions for the last five controller versions. Compatibility for older versions is available in those versions’ documentation.

Kong

By Kong, we are here referring to the official distribution of the Open-Source Kong Gateway.

Kubernetes Ingress Controller 1.2.x 1.3.x 2.0.x 2.1.x 2.2.x
Kong 1.0.x
Kong 1.1.x
Kong 1.2.x
Kong 1.3.x
Kong 1.4.x
Kong 1.5.x
Kong 2.0.x
Kong 2.1.x
Kong 2.2.x
Kong 2.3.x
Kong 2.4.x
Kong 2.5.x
Kong 2.6.x
Kong 2.7.x

Kong Enterprise

Kong Enterprise is the official enterprise distribution, which includes all other enterprise functionality, built on top of the Open-Source Kong Gateway.

Kubernetes Ingress Controller 1.2.x 1.3.x 2.0.x 2.1.x 2.2.x
Kong Enterprise 1.3.x
Kong Enterprise 1.5.x
Kong Enterprise 2.1.x
Kong Enterprise 2.2.x
Kong Enterprise 2.3.x
Kong Enterprise 2.4.x
Kong Enterprise 2.5.x
Kong Enterprise 2.6.x
Kong Enterprise 2.7.x

Kubernetes

Kubernetes Ingress Controller 1.2.x 1.3.x 2.0.x 2.1.x 2.2.x
Kubernetes 1.13
Kubernetes 1.14
Kubernetes 1.15
Kubernetes 1.16
Kubernetes 1.17
Kubernetes 1.18
Kubernetes 1.19
Kubernetes 1.20
Kubernetes 1.21
Kubernetes 1.22
Kubernetes 1.23

Istio

The Kubernetes Ingress Controller can be integrated with an Istio Service Mesh to use Kong Gateway as an ingress gateway for application traffic into the mesh network. See an example of this in the Istio Guide.

For each Kubernetes Ingress Controller release, tests are run to verify this documentation with upcoming versions of KIC and Istio. The following table lists the tested combinations:

Kubernetes Ingress Controller 1.2.x 1.3.x 2.0.x 2.1.x 2.2.x
Istio 1.6
Istio 1.7
Istio 1.8
Istio 1.9
Istio 1.10
Istio 1.11
Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2022