Install Kong Operator for Dev Portal

kubectl create namespace kong

If the namespace already exists, Kubernetes returns an AlreadyExists message, which is safe to ignore.

1. Add the Kong Helm charts:

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

   Copied!

2. Install Kong Operator using Helm:

   helm upgrade --install kong-operator kong/kong-operator -n kong-system \
     --create-namespace \
     --set image.tag=2.2 \
     --set env.ENABLE_CONTROLLER_KONNECT=true

   Copied!

   If you want cert-manager to issue and rotate the admission and conversion webhook certificates, install cert-manager to your cluster and enable cert-manager integration by passing the following argument while installing, in the next step:

   --set global.webhooks.options.certManager.enabled=true

   Copied!

   If you do not enable this, the chart will generate and inject self-signed certificates automatically. We recommend enabling cert-manager to manage the lifecycle of these certificates. Kong Operator needs a certificate authority to sign the certificate for mTLS communication between the control plane and the data plane. This is handled automatically by the Helm chart. If you need to provide a custom CA certificate, refer to the certificateAuthority section in the values.yaml of the Helm chart to learn how to create and reference your own CA certificate.

Wait for Kong Operator to be ready before moving on to the next step:

kubectl -n kong-system wait --for=condition=Available=true --timeout=120s deployment/kong-operator-kong-operator-controller-manager