Kong for Kubernetes

You can install Kong Ingress Controller with a single kubectl apply for testing purposes:

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

There are additional instructions for the following platforms:

• Minikube
• Google Kubernetes Engine(GKE) by Google
• Elastic Kubernetes Service(EKS) by Amazon
• Azure Kubernetes Service(AKS) by Microsoft

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/base
   

   You can use the above URL as a base kustomization and build on top of it to make it suite better for your cluster and use-case.

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  
   

1. 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
   

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-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