You are browsing documentation for an older version. See the latest documentation here.

Kong Ingress on Minikube

Setup Minikube

1. Install minikube

   Minikube is a tool that makes it easy to run Kubernetes locally. Minikube runs a single-node Kubernetes cluster inside a VM on your laptop to try out Kubernetes or develop with it day-to-day.

2. Start minikube

   minikube start
   

   It will take a few minutes to get all resources provisioned.

   kubectl get nodes
   

Deploy the Kong Ingress Controller

You can deploy the Kong Ingress Controller using kubectl or Helm:

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

helm repo add kong https://charts.konghq.com
helm repo update
helm install kong kong/ingress -n kong --create-namespace

The results should look like this:

   namespace/kong created
   customresourcedefinition.apiextensions.k8s.io/kongplugins.configuration.konghq.com created
   customresourcedefinition.apiextensions.k8s.io/kongconsumers.configuration.konghq.com created
   customresourcedefinition.apiextensions.k8s.io/kongcredentials.configuration.konghq.com created
   customresourcedefinition.apiextensions.k8s.io/kongingresses.configuration.konghq.com created
   serviceaccount/kong-serviceaccount created
   clusterrole.rbac.authorization.k8s.io/kong-ingress-clusterrole created
   clusterrolebinding.rbac.authorization.k8s.io/kong-ingress-clusterrole-nisa-binding created
   service/kong-proxy created
   service/kong-validation-webhook created
   deployment.apps/ingress-kong created
   deployment.apps/proxy-kong created
   ingressclass.networking.k8s.io/kong created

NAME: kong
LAST DEPLOYED: Tue Oct  3 15:12:38 2023
NAMESPACE: kong
STATUS: deployed
REVISION: 1
TEST SUITE: None

Note: this process could take up to five minutes the first time.

Setup environment variables

Next, set up an environment variable with the IP address at which Kong is accessible. This is used to send requests into the Kubernetes cluster.

The network is limited if you are using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly. When you deploy minikube on Linux with the Docker driver results in no tunnel being created. For more information, see accessing apps.

1. Run the minikube tunnel command in a separate terminal window and keep the tunnel open. This command creates a network route on the host to the service using the cluster’s IP address as a gateway. It exposes the external IP directly to any program running on the host operating system.

2. Get the IP address at which you can access Kong Gateway:

   kubectl

   Helm Charts

   $ minikube service -n kong kong-proxy --url | head -1

      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}')
      echo $HOST:$PORT

   The results should look like this:

   kubectl

   Helm Charts

   http://192.168.99.100:32728
      
   # The format of the URL is http://<HOST>:<PORT>.

   192.168.99.100:80

3. Set the environment variable. If you deployed using kubectl replace <HOST> with the IP address of Kong Gateway in the URL that you retrieved.

   kubectl

   Helm Charts

   export PROXY_IP=${HOST}:${PORT}

   export PROXY_IP=${HOST}:${PORT}

4. Verify that you can access Kong Gateway:

   curl -i $PROXY_IP
   

   The results should look like this:

   HTTP/1.1 404 Not Found
   Date: Wed, 06 Sep 2023 06:48:26 GMT
   Content-Type: application/json; charset=utf-8
   Connection: keep-alive
   Content-Length: 52
   X-Kong-Response-Latency: 0
   Server: kong/3.3.1
   
   {
     "message":"no Route matched with those values"
   }
   

   After you’ve installed the Kong Ingress Controller, please follow the getting started tutorial to learn about how to use the Ingress Controller.