{"id":32183,"date":"2022-12-06T08:35:01","date_gmt":"2022-12-06T08:35:01","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=32183"},"modified":"2022-12-23T05:44:42","modified_gmt":"2022-12-23T05:44:42","slug":"minikube-tutorials-minikube-tunnel-explained","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/minikube-tutorials-minikube-tunnel-explained\/","title":{"rendered":"Minikube Tutorials: minikube tunnel explained"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n
\n\n\n\n
\"\"<\/figure>\n\n\n\n

How to access applications running within minikube<\/h2>\n\n\n\n

There are two major categories of services in Kubernetes:<\/p>\n\n\n\n

    \n
  • NodePort<\/li>\n\n\n\n
  • LoadBalancer<\/li>\n<\/ul>\n\n\n\n

    NodePort access with Minikube<\/h2>\n\n\n\n

    A NodePort service is the most basic way to get external traffic directly to your service. NodePort, as the name implies, opens a specific port, and any traffic that is sent to this port is forwarded to the service.<\/p>\n\n\n\n

    Getting the NodePort using the service command: We also have a shortcut for fetching the minikube IP and a service\u2019s NodePort:
    $ minikube service –url<\/p>\n\n\n\n

    \n\n\n
    Example of<\/span> NodePort\n\nStep - 1<\/span>: Create a Kubernetes deployment\n$ kubectl create deployment hello-minikube1 --image=k8s.gcr.io\/echoserver:1.4<\/span>\n\nStep - 2<\/span>: Create a Kubernetes service type NodePort\n$ kubectl expose deployment hello-minikube1 --type=NodePort --port=8080<\/span>\n\nStep - 3<\/span>: Check Node Port\n$ kubectl get<\/span> svc\nNAME              TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE\nhello-minikube1   NodePort    10.100.238.34   <none>        8080:31389\/TCP   3s\n\nStep - 4: Run service tunnel\n$ minikube service hello-minikube1 --url\n\nStep - 5: To determine the NodePort for your service, you can use a kubectl command like this (note that nodePort begins with lowercase n in JSON output):\n$ kubectl get<\/span> service <service-name> --output='jsonpath=\"{.spec.ports[0<\/span>].nodePort}\"'<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    \n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \n\n\n\n
    \"\"<\/figure>\n\n\n\n
    \n\n\n\n
    Connect to LoadBalancer services with Minikube<\/h2>\n\n\n\n
    A LoadBalancer service is the standard way to expose a service to the internet. With this method, each service gets its own IP address.<\/p>\n\n\n\n
    Using minikube tunnel
    Services of type LoadBalancer can be exposed via the minikube tunnel command. It must be run in a separate terminal window to keep the LoadBalancer running. Ctrl-C in the terminal can be used to terminate the process at which time the network routes will be cleaned up<\/p>\n\n\n\n
    minikube tunnel creates a network route on the host to the service using the cluster\u2019s IP address as a gateway. The tunnel command exposes the external IP directly to any program running on the host operating system.<\/p>\n\n\n\n
    Note: The command requires root rights (sudo) because it creates a network configuration.<\/p>\n\n\n\n
    Tunnel is used to expose the service from inside of VM where minikube is running to the host machine’s network. Works with LoadBalancer service type.<\/p>\n\n\n\n
    Example of LoadBalancer with Minikube tunnel<\/p>\n\n\n\n
    \n\n\n
    Step 1<\/span> - Run the tunnel in<\/span> a separate terminal\n\nIt will ask for<\/span> a password.\n$ minikube tunnel\nminikube tunnel runs as<\/span> a process, creating a network route on the host to the service CIDR of<\/span> the cluster using the cluster\u2019s IP address as<\/span> a gateway. The tunnel command exposes the external IP directly to any program running on the host operating system.\n\ntunnel output example\n\n Password<\/span>:\n Status:\n machine: minikube\n pid<\/span>: 39087<\/span>\n route<\/span>: 10.96<\/span>.0<\/span>.0<\/span>\/12<\/span> -> 192.168<\/span>.64<\/span>.194<\/span>\n minikube<\/span>: Running\n services<\/span>: [hello-minikube]\n     errors<\/span>:\n   minikube: no errors\n   router<\/span>: no errors\n   loadbalancer emulator: no errors\n\n\nStep 2<\/span> - Create a Kubernetes deployment\n$ kubectl create deployment hello-minikube1 --image=k8s.gcr.io\/echoserver:1.4<\/span>\n\nStep 3<\/span> - Create a Kubernetes service with<\/span> type LoadBalancer\n\nkubectl expose deployment hello-minikube1 --type=LoadBalancer --port=8080<\/span>\n\nStep 4<\/span> - Check the external IP\n$ kubectl get<\/span> svc\n$ kc get<\/span> svc\n NAME              TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)          AGE\n hello-minikube1   LoadBalancer   10.96.184.178   10.96.184.178   8080:30791\/TCP   40s\n \nNote that without minikube tunnel, Kubernetes will show the external IP as \u201cpending\u201d.\n\nStep 5 - Try in your browser\n\nOpen in your browser (ensure there is no proxy set<\/span>)\n\nhttp://REPLACE_WITH_EXTERNAL_IP:8080\nEach service will get<\/span> its own external IP.<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    \n","protected":false},"excerpt":{"rendered":"
    How to access applications running within minikube There are two major categories of services in Kubernetes: NodePort access with Minikube A NodePort service is the most basic way to get external traffic directly to your service. NodePort, as the name implies, opens a specific port, and any traffic that is sent to this port is…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-32183","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/32183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=32183"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/32183\/revisions"}],"predecessor-version":[{"id":32194,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/32183\/revisions\/32194"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=32183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=32183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=32183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}