Use Kong for Kubernetes Gateway API or Ingress. Configure plugins, health checking, load balancing and more, all using Custom Resource Definitions (CRDs) and Kubernetes-native tooling.
Features | Get started | Documentation | main branch builds | Seeking help
- Gateway API support Use Gateway API resources (official successor of Ingress resources) to configure Kong. Native support for TCP, UDP, TLS, gRPC and HTTP/HTTPS traffic, reuse the same gateway for multiple protocols and namespaces.
- Ingress support Use Ingress resources to configure Kong.
- Declarative configuration for Kong Configure all of Kong features in declarative Kubernetes native way with CRDs.
- Seamlessly operate Kong Scale and manage multiple replicas of Kong Gateway automatically to ensure performance and high-availability.
- Health checking and load-balancing Load balance requests across your pods and supports active & passive health-checks.
- Enhanced API management using plugins
Use a wide array of plugins for e.g.
- authentication
- request/response transformations
- rate-limiting
You can use Minikube or Kind on your local machine or use a hosted Kubernetes service like GKE.
Setting up Kong for Kubernetes is as simple as:
# Install the Gateway API CRDs before installing Kong Ingress Controller.
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml
# Install the Kong Ingress Controller with Helm.
helm install kong --namespace kong --create-namespace --repo https://charts.konghq.com ingressTo learn more details about Helm chart follow the Helm chart documentation.
Once installed, please follow the Getting Started guide to start using Kong in your Kubernetes cluster.
Note: Kong Enterprise users, please follow along with our enterprise guide to setup the enterprise version.
Release builds of Kong Ingress Controller can be found on Docker Hub in kong/kubernetes-ingress-controller repository.
At the moment we're providing images for:
- Linux
amd64 - Linux
arm64
Nightly pre-release builds of the main branch are available from the
kong/nightly-ingress-controller repository hosted on Docker Hub:
main contains unreleased new features for upcoming minor and major releases:
docker pull kong/nightly-ingress-controller:nightlyAll documentation for the Kong Ingress Controller is present in the kong/docs.konghq.com repository. Pull Requests are welcome for additions and corrections.
Please browse through the guides to get started and to learn specific ingress controller operations.
We ❤️ pull requests and we’re continually working hard to make it as easy as possible for developers to contribute. Before beginning development with the Kong Ingress Controller, please familiarize yourself with the following developer resources:
Please search through the FAQs, posts on the discussions page or the Kong Nation Forums as it's likely that another user has run into the same problem. If you don't find an answer, please feel free to post a question.
If you've found a bug, please open an issue.
For a feature request, please open an issue using the feature request template.
You can also talk to the developers behind Kong in the #kong channel on the Kubernetes Slack server.
You can join monthly meetups hosted by Kong to ask questions, provide feedback, or just to listen and hang out. See the Online Meetups Page to sign up and receive meeting invites and Zoom links.
At any time the KIC may include features or options that are considered experimental and are not enabled by default, nor available in the Kong Documentation Site.
To try out new features that are behind feature gates, please see the preview features in FEATURE_GATES.md and documentation for these preview features can be found in FEATURE_PREVIEW_DOCUMENTATION.md.