Install on Kubernetes with Helm

    • The Enterprise deployment includes a Postgres sub-chart provided by Bitnami.
    • For open-source deployments, you can choose to use the Postgres sub-chart, or install without a database.

    Configuration for both options is flexible and depends on your environment.

    The documentation on installing with a flat Kubernetes manifest also explains how to install in DB-less mode for both Enterprise and OSS deployments.

    The Kong Gateway software is governed by the . Kong Gateway (OSS) is licensed under an Apache 2.0 license.

    • A Kubernetes cluster, v1.19 or later
    • v1.19 or later
    • (Enterprise only) A license.json file from Kong
    • Helm 3

    Create namespace

    Create the namespace for Kong Gateway with Kubernetes Ingress Controller. For example:

    Set up Helm

    1. Add the Kong charts repository:

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

    1. Save your license file temporarily with the filename license (no file extension).

    2. Run:

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

    Create secret for RBAC superuser (recommended)

    If you plan to use RBAC, you must create a secret for the superuser account password at this step in installation. You cannot create it later.

    1. Create the RBAC account.

      1. kubectl create secret generic kong-enterprise-superuser-password \
      2. -n kong \
      3. --from-literal=password={YOUR_PASSWORD}

    Create secret for Session plugin

    If you create an RBAC superuser and plan to work with Kong Manager or Dev Portal, you must also configure the Session plugin and store its config in a Kubernetes secret:

    1. Create a session config file for Kong Manager:

      1. $ echo '{"cookie_name":"admin_session","cookie_samesite":"off","secret":"<your-password>","cookie_secure":false,"storage":"kong"}' > admin_gui_session_conf

    2. Create a session config file for Kong Dev Portal:

      Or, if you have different subdomains for the portal_api_url and portal_gui_host, set the cookie_domain and properties as follows:

      1. $ echo '{"cookie_name":"portal_session","cookie_samesite":"off","cookie_domain":"<.your_subdomain.com">,"secret":"<your-password>","cookie_secure":false,"storage":"kong"}' > portal_session_conf

    3. Create the secret:

      For Kong Manager only:

      1. kubectl create secret generic kong-session-config \
      2. -n kong \
      3. --from-file=admin_gui_session_conf

      For Kong Manager and Dev Portal:

      1. kubectl create secret generic kong-session-config \
      2. --from-file=admin_gui_session_conf \
      3. --from-file=portal_session_conf

    Create a values.yaml file to provide required values such as password secrets or optional email addresses for notifications. You can work from the . The example file includes comments to explain which values you must set.

    For OSS deployments, the default install might be sufficient, but you can explore other values.yaml files and the readme in the charts repository, which includes an exhaustive list of all possible configuration properties.

    Note that the Enterprise deployment includes a Postgres sub-chart provided by Bitnami. You might need to delete the PersistentVolume objects for Postgres in your Kubernetes cluster to connect to the database after install.

    Deploy Kong Gateway with Kubernetes Ingress Controller

      1. ## Kong Gateway
      2. helm install my-kong kong/kong -n kong --values ./values.yaml
      2. helm install kong/kong --generate-name --set ingressController.installCRDs=false

      For more information on working with Helm charts for Kong Gateway (OSS), see the chart documentation.

      This might take some time.

    2. Check pod status, and make sure the my-kong-kong-{ID} pod is running:

    Finalize configuration and verify installation

    1. Run:

      1. kubectl get svc my-kong-kong-admin \
      2. -n kong \
      3. --output=jsonpath='{.status.loadBalancer.ingress[0].ip}'

    2. Copy the IP address from the output, then add the following to the .env section of your values.yaml file:

      1. admin_api_uri: {YOUR-DNS-OR-IP}

    3. Clean up:

      1. kubectl delete jobs -n kong --all

    4. Update with changed values.yaml:

      1. helm upgrade my-kong kong/kong -n kong --values ./values.yaml