Introduction
Kong for Kubernetes Enterprise provides most Kong Enterprise plugins and runs without a database, but does not include other Kong Enterprise features (Kong Manager, Dev Portal, Vitals, etc).
Note: See Kong for Kubernetes deployment options for a feature breakdown and image comparison.
You can install Kong for Kubernetes Enterprise using YAML with kubectl, or with OpenShift oc. Other deployment options, such as using Helm Chart and Kustomize, will be available at a later time.
Prerequisites
Before starting installation, be sure you have the following:
Prerequisites
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. - A valid Bintray account with access to the Kong repository. You receive access
when you begin a paid Kong Enterprise subscription.
- You will need your username, account password, account API Key,
and Kong Enterprise license file. For example:
- Bintray username:
john-company@kong
- Bintray password:
12345678
- Bintray API key:
12234e314356291a2b11058591bba195830
- Bintray username:
- To find the API Key, go to https://bintray.com/profile/edit and select API Key.
- To find the Kong Enterprise license JSON file, log into your Bintray
account and go to
https://bintray.com/kong/<YOUR_REPO_NAME>/license#files
. For more details, see Accessing Your License.
- You will need your username, account password, account API Key,
and Kong Enterprise license file. For example:
Step 1. Provision a Namespace
To create the secrets for license and Docker registry access,
first provision the kong
namespace:
Step 2. Set Up Kong Enterprise License
Running Kong for Kubernetes Enterprise requires a valid license. 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.
Step 3. Configure Kong Enterprise Docker registry access
Set up Docker credentials to allow Kubernetes nodes to pull down the Kong Enterprise Docker image, which is hosted in a private repository. You receive credentials for the Kong Enterprise Docker image when you sign up for Kong Enterprise.
Step 4. Deploy Kong for Kubernetes Enterprise
The steps in this section show you how to install Kong for Kubernetes Enterprise using YAML.
Note: Depending on the Kubernetes distribution you are using, you may or may not see an external IP address assigned to the service. See 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, see the getting started tutorial.
Next steps…
See Using Kong for Kubernetes Enterprise for information about concepts, how-to guides, reference guides, and using plugins.