PermalinkInstalling Kong for Kubernetes Enterprise
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.
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
oroc
(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:
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:
- 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.
The initial setup might take a few minutes.
You can also see the kong-proxy service:
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.