Install Kong Ingress Controller with Helm

Kong Ingress Controller is installed using the kong/ingress Helm chart.

The kong/ingress chart is a wrapper around kong/kong that manages separate Kong Ingress Controller and Kong Gateway deployments automatically.

You can use any of the configuration options available in the kong/kong chart when using the kong/ingress chart.

• To configure the Kong Ingress Controller deployment, place the keys from kong/kong under a controller key in the values.yaml file.

controller:
  ingressController:
    image:
      repository: kong/kubernetes-ingress-controller
      tag: "3.3.1"

• To configure the Kong Gateway deployment, place the keys from kong/kong under a gateway key in the values.yaml file.

gateway:
  env:
    router_flavor: expressions

Installation

Install the Gateway APIs

1. Install the Gateway API CRDs before installing Kong Ingress Controller.

    kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.1.0/standard-install.yaml
   

2. Create a Gateway and GatewayClass instance to use.

   echo "
   ---
   apiVersion: gateway.networking.k8s.io/v1
   kind: GatewayClass
   metadata:
     name: kong
     annotations:
       konghq.com/gatewayclass-unmanaged: 'true'
   
   spec:
     controllerName: konghq.com/kic-gateway-controller
   ---
   apiVersion: gateway.networking.k8s.io/v1
   kind: Gateway
   metadata:
     name: kong
   spec:
     gatewayClassName: kong
     listeners:
     - name: proxy
       port: 80
       protocol: HTTP
       allowedRoutes:
         namespaces:
            from: All
   " | kubectl apply -f -
   

   The results should look like this:

   gatewayclass.gateway.networking.k8s.io/kong created
   gateway.gateway.networking.k8s.io/kong created
   

Install Kong

You can install Kong in your Kubernetes cluster using Helm.

1. Add the Kong Helm charts:

    helm repo add kong https://charts.konghq.com
    helm repo update
   

2. Install Kong Ingress Controller and Kong Gateway with Helm:

   Kong Gateway

   Kong Gateway (OSS)

   helm install kong kong/ingress -n kong --create-namespace

   helm install kong kong/ingress -n kong --create-namespace --set gateway.image.repository=kong --set gateway.image.tag="3.8.1"

Test connectivity to Kong

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:

1. Populate $PROXY_IP for future commands:

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

2. Ensure that you can call the proxy IP:

    curl -i $PROXY_IP
   

   The results should look like this:

    HTTP/1.1 404 Not Found
    Content-Type: application/json; charset=utf-8
    Connection: keep-alive
    Content-Length: 48
    X-Kong-Response-Latency: 0
    Server: kong/3.0.0
     
    {"message":"no Route matched with those values"}