Skip to content
2023 API Summit Hackathon: Experiment with AI for APIs (August 28 - September 27) Learn More →
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Insomnia
      Collaborative API development platform
      Kuma
      Open-source distributed control plane with a bundled Envoy Proxy integration
      Docs Contribution Guidelines
      Want to help out, or found an issue in the docs and want to let us know?
  • API Specs
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
Kong Ingress Controller
2.6.x
  • Home icon
  • Kong Ingress Controller
  • Deployment
  • Kong Ingress on Minikube
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 2.11.x (latest)
  • 2.10.x
  • 2.9.x
  • 2.8.x
  • 2.7.x
  • 2.6.x
  • 2.5.x
  • 2.4.x
  • 2.3.x
  • 2.2.x
  • 2.1.x
  • 2.0.x
  • 1.3.x
  • 1.2.x
  • 1.1.x
  • 1.0.x
enterprise-switcher-icon Switch to OSS
On this pageOn this page
  • Setup Minikube
  • Deploy the Kong Ingress Controller
  • Setup environment variables
  • Troubleshooting connection issues
    • Error message
    • Work around
You are browsing documentation for an outdated 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
Helm Charts
$ kubectl create -f https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v2.6.0/deploy/single/all-in-one-dbless.yaml
helm repo add kong https://charts.konghq.com
helm repo update
helm install kongdocs kong/kong

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
configmap/kong-server-blocks created
service/kong-proxy created
service/kong-validation-webhook created
deployment.extensions/kong created

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.

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

    $ minikube service -n kong kong-proxy --url | head -1
    # If installed by helm, service name would be "<release-name>-kong-proxy".
    # minikube service <release-name>-kong-proxy --url | head -1
    

    The results should look like this:

    http://192.168.99.100:32728
    
  2. Set the environment variable. Replace <ip-address> with the Kong Gateway IP address you just retrieved:

    export PROXY_IP=<ip-address>
    echo $PROXY_IP
    
  3. 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.

Troubleshooting connection issues

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.

Error message

curl: (7) Failed to connect to 127.0.0.1 port 80 after 5 ms: Couldn't connect to server

Work around

Run the minikube tunnel command in a separate terminal window to 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.

Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023