Skip to content
Kong Logo | Kong Docs Logo
  • Docs
    • Explore the API Specs
      View all API Specs View all API Specs View all API Specs arrow image
    • Documentation
      API Specs
      Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong AI Gateway
      Multi-LLM AI Gateway for GenAI infrastructure
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Kong Gateway Operator
      Manage your Kong deployments on Kubernetes using YAML Manifests
      Insomnia
      Collaborative API development platform
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      AI's icon
      AI
      Govern, secure, and control AI traffic with multi-LLM AI Gateway plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
Kong Ingress Controller
2.10.x
  • Home icon
  • Kong Ingress Controller
  • Deployment
  • Kong for Kubernetes Enterprise
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Kong AI Gateway
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • unreleased
  • 3.4.x (latest) (LTS)
  • 3.3.x
  • 3.2.x
  • 3.1.x
  • 3.0.x
  • 2.12.x (LTS)
  • 2.11.x
  • 2.10.x
  • 2.9.x
  • 2.8.x
  • 2.7.x
  • 2.6.x
  • 2.5.x (LTS)
  • Introduction
    • FAQ
    • Version Support Policy
    • Stages of Software Availability
    • Changelog
  • Concepts
    • Architecture
    • Custom Resources
    • Deployment Methods
    • Kong for Kubernetes with Kong Gateway Enterprise
    • High-Availability and Scaling
    • Resource Classes
    • Security
    • Ingress Resource API Versions
    • Gateway API
    • Expression Based Router
  • Deployment
    • Kong Ingress on Minikube
    • Kong for Kubernetes
    • Kong Enterprise for Kubernetes (DB-less)
    • Kong Enterprise for Kubernetes (DB-backed)
    • Kong Ingress on AKS
    • Kong Ingress on EKS
    • Kong Ingress on GKE
    • Admission Webhook
    • Installing Gateway APIs
  • Guides
    • Getting Started with KIC
    • Upgrading from previous versions
    • Upgrading to Kong 3.x
    • Using Kong Gateway Enterprise
    • Getting Started using Istio
    • Using Custom Resources
      • Using the KongPlugin Resource
      • Using the KongIngress Resource
      • Using KongConsumer and KongCredential Resources
      • Using the TCPIngress Resource
      • Using the UDPIngress Resource
    • Using the ACL and JWT Plugins
    • Using cert-manager with Kong
    • Allowing Multiple Authentication Methods
    • 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
    • Setting up Upstream mTLS
    • Exposing a TCP/UDP/gRPC Service
      • Exposing a TCP Service
      • Exposing a UDP Service
      • Exposing a gRPC service
    • Using the mTLS Auth Plugin
    • Using the OpenID Connect Plugin
    • Rewriting Hosts and Paths
    • Preserving Client IP Address
    • Using Kong with Knative
    • Using Multiple Backend Services
    • Using Gateway Discovery
    • Routing by Header
  • References
    • KIC Annotations
    • CLI Arguments
    • Custom Resource Definitions
    • Plugin Compatibility
    • Version Compatibility
    • Supported Kong Router Flavors
    • Troubleshooting
    • Kubernetes Events
    • Prometheus Metrics
    • Feature Gates
    • Supported Gateway API Features
enterprise-switcher-icon Switch to OSS
On this pageOn this page
  • Before you begin
    • Kong Gateway Enterprise License secret
    • Installing Kong Gateway Enterprise
You are browsing documentation for an older version. See the latest documentation here.

Kong for Kubernetes Enterprise

Kong for Kubernetes Enterprise is an enhanced version of the Open-Source Ingress Controller. It includes all Enterprise plugins and comes with 24x7 support for worry-free production deployment. This is available only for enterprise customers of Kong, Inc.

Before you begin

  1. Create the kong namespace in the cluster to create a secret.

     $ kubectl create namespace kong
    

    The results should look like this:

     namespace/kong created
    
  2. Create Kong Gateway Enterprise License secret

Kong Gateway Enterprise License secret

Enterprise version requires a valid license to run. As part of sign up for Kong Gateway Enterprise, you should have received a license file. If you do not have one, please contact your sales representative.

  1. Save the license file temporarily to disk with filename license.json.
  2. Deploy Kong Gateway Enterprise in the kong namespace. Ensure that you provide the file path where you have stored license.json file when you run the command. To deploy Kong Ingress Controller in a different namespace, change the value of -n kong.

     $ kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong
    

    The results should look like this:

     secret/kong-enterprise-license created
    

Installing Kong Gateway Enterprise

Kong for Kubernetes Enterprise can be installed using an installer of your choice. After the installation is complete, see the getting started tutorial to learn more.

YAML manifests
Kustomize
Helm
  1. Install Kong for Kubernetes Enterprise using YAML manifests.

     kubectl apply -f https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v2.10.5/deploy/single/all-in-one-dbless-k4k8s-enterprise.yaml
    

    The results should look like this:

     role.rbac.authorization.k8s.io/kong-leader-election created
     clusterrole.rbac.authorization.k8s.io/kong-ingress created
     clusterrole.rbac.authorization.k8s.io/kong-ingress-crds created
     clusterrole.rbac.authorization.k8s.io/kong-ingress-gateway created
     clusterrole.rbac.authorization.k8s.io/kong-ingress-knative created
     rolebinding.rbac.authorization.k8s.io/kong-leader-election created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-crds created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-gateway created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-knative created
     service/kong-admin created
     service/kong-proxy created
     service/kong-validation-webhook created
     deployment.apps/ingress-kong created
     deployment.apps/proxy-kong created
     ingressclass.networking.k8s.io/kong created
    
  2. Check if the Kong Ingress Controller is ready.
     $ kubectl get pods -n kong
    

    The results should look like this:

     NAME                            READY   STATUS    RESTARTS   AGE
     ingress-kong-6ffcf8c447-5qv6z   2/2     Running   1          44m
    

    It takes a few minutes the first time you set this up.

  3. Check if the kong-proxy service is deployed.

     $ kubectl get service kong-proxy -n kong
    

    The results should look like this:

     NAME         TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)                      AGE
     kong-proxy   LoadBalancer   10.63.254.78   192.168.99.100   80:32697/TCP,443:32365/TCP   22h
    

    Note: Depending on the Kubernetes distribution you are using, you might or might not see an external IP address assigned to the service. To obtain an IP address for a Kubernetes Service of type LoadBalancer, see your cloud provider’s documentation.

  4. Kubernetes exposes the proxy through a Kubernetes service. Run the following commands to store the load balancer IP address in a variable named PROXY_IP:

     $ export PROXY_IP=$(kubectl get -o jsonpath="{.status.loadBalancer.ingress[0].ip}" service -n kong kong-proxy)
     echo $PROXY_IP
    

    The results should look like this:

     192.168.99.100
    

    Note: It may take a while for your cloud provider to actually associate the IP address to the kong-proxy Service.

Kustomize manifests are provided for illustration purposes only and are not officially supported by Kong. There is no guarantee of backwards compatibility or upgrade capabilities for our Kustomize manifests. For a production setup with Kong support, use the Helm chart.

  1. Install Kong for Kubernetes using Kustomize:

     kubectl apply -k github.com/kong/kubernetes-ingress-controller/config/variants/enterprise
    

    You can use this as a base kustomization and build on top of it for your cluster and use-case.

    The results should look like this:

     role.rbac.authorization.k8s.io/kong-leader-election created
     clusterrole.rbac.authorization.k8s.io/kong-ingress created
     clusterrole.rbac.authorization.k8s.io/kong-ingress-crds created
     clusterrole.rbac.authorization.k8s.io/kong-ingress-gateway created
     clusterrole.rbac.authorization.k8s.io/kong-ingress-knative created
     rolebinding.rbac.authorization.k8s.io/kong-leader-election created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-crds created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-gateway created
     clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-knative created
     service/kong-admin created
     service/kong-proxy created
     service/kong-validation-webhook created
     deployment.apps/ingress-kong created
     deployment.apps/proxy-kong created
     ingressclass.networking.k8s.io/kong created
    
  2. Kubernetes exposes the proxy through a Kubernetes service. Run the following commands to store the load balancer IP address in a variable named PROXY_IP:

     HOST=$(kubectl get svc --namespace kong kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
     PORT=$(kubectl get svc --namespace kong kong-proxy -o jsonpath='{.spec.ports[0].port}')
     export PROXY_IP=${HOST}:${PORT}
     echo $PROXY_IP  
    

    The results should look like this:

     192.168.99.100:80
    

You can use Helm to install Kong using the official Helm chart:

  1. Create a values.yaml file with these details to deploy using Helm charts.
     gateway:
         image:
           repository: kong/kong-gateway
           tag: 3.10.0.1
         env:
           LICENSE_DATA:
             valueFrom:
               secretKeyRef:
                 name: kong-enterprise-license
                 key: license
    
  2. Install Kong Ingress Controller and Kong Gateway with Helm:

     $ helm repo add kong https://charts.konghq.com
     $ helm repo update
     $ helm install kong kong/ingress -n kong --create-namespace --values ./values.yaml
    

    The results should look like this:

     NAME: kong
     LAST DEPLOYED: Fri Oct  6 14:41:16 2023
     NAMESPACE: kong
     STATUS: deployed
     REVISION: 1
     TEST SUITE: None
    
  3. Kubernetes exposes the proxy through a Kubernetes service. Run the following commands to store the load balancer IP address in a variable named PROXY_IP:

     HOST=$(kubectl get svc --namespace kong kong-gateway-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
     PORT=$(kubectl get svc --namespace kong kong-gateway-proxy -o jsonpath='{.spec.ports[0].port}')
     export PROXY_IP=${HOST}:${PORT}
     echo $PROXY_IP   
    

    The results should look like this:

     192.168.99.100:80
    
Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • Kong
    Powering the API world

    Increase developer productivity, security, and performance at scale with the unified platform for API management, service mesh, and ingress controller.

    • Products
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • Product Updates
      • Get Started
    • Documentation
      • Kong Konnect Docs
      • Kong Gateway Docs
      • Kong Mesh Docs
      • Kong Insomnia Docs
      • Kong Konnect Plugin Hub
    • Open Source
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kong Community
    • Company
      • About Kong
      • Customers
      • Careers
      • Press
      • Events
      • Contact
  • Terms• Privacy• Trust and Compliance
© Kong Inc. 2025