Kong Ingress Controller for Kubernetes

Use Kong for Kubernetes Ingress.Configure plugins, health checking,load balancing and more in Kongfor Kubernetes Services, all usingCustom Resource Definitions(CRDs) and Kubernetes-native tooling.

Features | Get started | Documentation | main branch builds | Seeking help

✨ KIC 2.0 is in public beta! ✨

We're happy to announce that Kong Ingress Controller 2.0 is in public beta.

This new release comes with a major internal rearchitecture, and the following added features:

• Support for UDP ingress resources and the new UDPIngress CRD,
• Ingress controller runtime metrics compatible with Prometheus, for easier monitoring and alerting.

For a quick start, just deploy KIC 2.0 beta to your cluster:

$ kubectl apply -f "https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/main/deploy/single-v2/all-in-one-dbless.yaml"

See the documentation for Kong Ingress Controller 2.0 beta.

Features

• Ingress routingUse Ingress resources to configure Kong
• Enhanced API management using pluginsUse a wide-array of pluginsto monitor, transform, protect your traffic.
• Native gRPC supportProxy gRPC traffic and gain visibility into it usingKong's plugin.
• Health checking and Load-balancingLoad balance requests across your pods and supports active & passive health-checks.
• Request/response transformationsUse plugins tomodify your requests/responses on the fly.
• AuthenticationProtect your services using authentication methodsof your choice.
• Declarative configuration for KongConfigure all of Kongusing CRDs in Kubernetes and manage Kong declaratively.

Get started

You can useMinikube, Kindon your local machine or usea hosted k8s service likeGKE.

Setting up Kong for Kubernetes is as simple as:

# using YAMLs
$ kubectl apply -f https://bit.ly/k4k8s

# or using Helm
$ helm repo add kong https://charts.konghq.com
$ helm repo update

# Helm 3
$ helm install kong/kong --generate-name --set ingressController.installCRDs=false

Once installed, please follow the Getting Started guideto start using Ingress in your Kubernetes cluster.

Note: Kong Enterprise users, please follow along ourenterprise guide to setup the enterprise version.

Contributing

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, please familiarize yourself with the following developer resources:

• CONTRIBUTING
• CODE_OF_CONDUCT and COPYRIGHT

Documentation

All documentation around Kong Ingress Controller is present in thisrepository inside the docs directory.Pull Requests are welcome for additions and corrections.

Guides and Tutorials

Please browse through guides to get started or understand how to configurea specific setting with Kong Ingress Controller.

main branch builds

Pre-release builds of the main branch are available from thekong-ingress-controller repository hosted on Docker Hub:

main contains unreleased new features for upcoming minor and major releases:

docker pull kong/kubernetes-ingress-controller:main

Seeking help

Please search through the posts onKong Nation as it'slikely that another user has run into the same problem.If you don't find an answer, please feel free to post a question.For a feature request, please post inFeature Suggestionscategory.

You can also talk to the developers behind Kong in the#kong channel on theKubernetes Slack server.

If you've spotted a bug, please open an issueon our Github.

Community meetings

You can join monthly meetings hosted by the maintainers of the projectto ask questions, provide feedback or just come and say hello.The meeting takes place on every second Tuesday of the monthat 10 am Pacific time.Please submit your contact details on theonline meetups page to receivemeeting invite and Zoom links to join the meeting.