Kong Application Security
The Kong Ingress controller and CloudGuard WAF for Kubernetes agent are deployed together with a single Helm chart. The configuration of the Kong Ingress controller is done with common methods for configuring Ingress using both Kubernetes Ingress resources or Kong Ingress resources.
This diagram shows an example of a Kubernetes service exposed outside the Kubernetes cluster with an Kong Ingress controller protected with CloudGuard WAF.
Prerequisites
Kong version 1.22.0+ cluster with RBAC enabled with Cluster admin permissions
Helm 3 Package Manager installed on your local machine
The
kubectl
andwget
command-line tools installed on your bastion or platform that you use to access the Kubernetes cluster
Installation
Step 1: Download Helm chart
Run the following command depending on your Kubernetes version:
wget https://github.com/CheckPointSW/Infinity-Next/raw/main/deployments/cp-k8s-appsec-kong-2.22.0.tgz -O cp-k8s-appsec-kong-2.22.0.tgz
Step 2: Install Helm chart
Make sure you obtained the token from the Enforcement Profile page first, you will need it in the command to deploy the Helm chart.
Run the following command depending on your Kubernetes version (Note - package file names contain the name appsec - short for "Application Security" provided by CloudGuard WAF):
helm install cp-k8s-appsec-kong-2.22.0.tgz --name-template cp-appsec --set appsec.agentToken="<token>" --create-namespace -n kong
Step 3: Create SSL/TLS Secret (optional if the servers do not use HTTPS)
Kubernetes Secrets are used for TLS termination of the Ingress resource. The public/private key pair must already exist before creating the Secret. Read more about Kubernetes TLS Secrets in the Official Kubernetes Documentation.
Create a Kubernetes SSL/TLS Secret using the following command with the public key certificate for --cert
.PEM-encoded and matching the private key for --key
:
kubectl create secret tls <certificate-name> --key <private-key-file> --cert $<certificate-file>
Step 4: Configure the Ingress resource
Edit your ingress.yaml with your favorite editor
If needed add the following annotation:
kubernetes.io/ingress.class: "nginx"
Step 5: Deploy the Ingress
In environments that can allow short downtime, uninstall the older ingress and install the new one.
kubectl apply -f ingress.yaml
In environments that require zero-downtime:
Redirect your DNS traffic from the old ingress to the new ingress
Log traffic from both controllers during this changeover
Uninstall the old ingress once traffic has fully drained from it
Last updated
Was this helpful?