Skip to content
|
You are browsing the Kong Gateway documentation archive. This documentation is no longer actively maintained.
See the latest Kong Gateway documentation.
Kong Gateway Enterprise [ARCHIVE]
2.5.x

PermalinkInstalling Kong for Kubernetes Enterprise

Note: This deployment option is not supported in free mode.

PermalinkIntroduction

Kong for Kubernetes Enterprise provides most Kong Gateway plugins and runs without a database, but does not include other Enterprise features (Kong Manager, Dev Portal, Vitals, and so on).

This installation topic walks you through a DB-less deployment on Kubernetes. For the full range of Enterprise features, you need a database-backed or a hybrid deployment. See the instructions for Installing Kong Gateway on Kubernetes, which walk you through a deployment with a database.

Note: See Kong for Kubernetes deployment options for a feature breakdown and comparison between DB-less and database-backed deployments.

Kong for Kubernetes Enterprise

You can install Kong for Kubernetes Enterprise using YAML with kubectl, with OpenShift oc, or with Helm.

This software is governed by the Kong Software License Agreement.

PermalinkDeployment options

The following instructions assume that you are deploying Kong Gateway in classic embedded mode.

If you would like to run Kong Gateway in Hybrid mode, the instructions in this topic will walk you though setting up a Control Plane instance. Afterward, you will need to bring up additional gateway instances for the Data Planes, and perform further configuration steps. See Hybrid Mode setup documentation for details.

PermalinkPrerequisites

Before starting installation, be sure you have the following:

  • Kubernetes cluster: Kong is compatible with all distributions of Kubernetes. You can use a Minikube, GKE, or OpenShift cluster.
  • kubectl or oc access: You should have kubectl or oc (if working with OpenShift) installed and configured to communicate to your Kubernetes cluster.
  • Enterprise customers: If you have a paid Kong Konnect subscription and are not running Kong Gateway in free mode, you should have received a license.json file from Kong.

PermalinkStep 1. Provision a namespace

To create the license secret, first provision the kong namespace:

$ kubectl create namespace kong

$ oc new-project kong

PermalinkStep 2. (Optional) Set up license

If you plan on using a license to unlock Enterprise features, see prerequisites for more information.

Save the license file temporarily to disk with filename license (no file extension) and execute the following:

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

$ oc create secret generic kong-enterprise-license --from-file=./license -n kong
Note:
  • There is no .json extension in the --from-file parameter.
  • -n kong specifies the namespace in which you are deploying Kong for Kubernetes Enterprise. If you are deploying in a different namespace, change this value.

PermalinkStep 3. Deploy Kong for Kubernetes Enterprise

The steps in this section show you how to install Kong for Kubernetes Enterprise using YAML.

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

$ oc create -f https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v2.4.0/deploy/single/all-in-one-dbless-k4k8s-enterprise.yaml

The initial setup might take a few minutes.

$ kubectl get pods -n kong

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

$ oc get pods -n kong

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

You can also see the kong-proxy service:

$ kubectl get service kong-proxy -n kong

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

$ oc get service kong-proxy -n kong

NAME         TYPE           CLUSTER-IP     EXTERNAL-IP     PORT(S)                      AGE
kong-proxy   LoadBalancer   10.63.254.78   35.233.198.16   80:32697/TCP,443:32365/TCP   22h
Note: Depending on the Kubernetes distribution you are using, you might see an external IP address assigned to the service. Refer to your provider's guide on obtaining an IP address for a Kubernetes Service of type LoadBalancer.

Set up an environment variable to hold the IP address:

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

It might take a while for your cloud provider to associate the IP address to the kong-proxy service. After you have installed Kong Gateway, see the getting started tutorial.

PermalinkNext steps

See the Kong Ingress Controller docs for information about concepts, how-to guides, reference guides, and using plugins. for information about concepts, how-to guides, reference guides, and using plugins.