Kubernetes (Minikube) external ip does not work

Question

I am new to Kubernetes and i have been browsing looking and reading why my external ip is not resolving.

I am running minikube on a ubuntu 16.04 distro.

In the services overview of the dashboard i have this

    my-nginx | run: my-nginx | 10.0.0.11 | my-nginx:80 TCP my-nginx:32431 | TCP 192.168.42.71:80

When i do an http get at http://192.168.42.165:32431/ i get the nginx page.

The configuration of the service is as follows

    # Please edit the object below. Lines beginning with a '#' will be ignored,
    # and an empty file will abort the edit. If an error occurs         while saving this file will be
    # reopened with the relevant failures.
    #
    apiVersion: v1
    kind: Service
    metadata:
      creationTimestamp: 2016-09-23T12:11:13Z
      labels:
        run: my-nginx
      name: my-nginx
      namespace: default
      resourceVersion: "4220"
      selfLink: /api/v1/namespaces/default/services/my-nginx
      uid: d24b617b-8186-11e6-a25b-9ed0bca2797a
    spec:
      clusterIP: 10.0.0.11
      deprecatedPublicIPs:
      - 192.168.42.71
      externalIPs:
      - 192.168.42.71
      ports:
      - nodePort: 32431
        port: 80
        protocol: TCP
        targetPort: 80
      selector:
        run: my-nginx
      sessionAffinity: None
      type: LoadBalancer
    status:
      loadBalancer: {}

These are parts of my ifconfog

    virbr0    Link encap:Ethernet  HWaddr fe:54:00:37:8f:41  
              inet addr:192.168.122.1  Bcast:192.168.122.255          Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:4895 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8804 errors:0 dropped:0 overruns:0         carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:303527 (303.5 KB)  TX bytes:12601315 (12.6         MB)

    virbr1    Link encap:Ethernet  HWaddr fe:54:00:9a:39:74  
              inet addr:192.168.42.1  Bcast:192.168.42.255          Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:7462 errors:0 dropped:0 overruns:0 frame:0
              TX packets:12176 errors:0 dropped:0 overruns:0         carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:3357881 (3.3 MB)  TX bytes:88555007 (88.5 MB)


    vnet0     Link encap:Ethernet  HWaddr fe:54:00:37:8f:41  
              inet6 addr: fe80::fc54:ff:fe37:8f41/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:4895 errors:0 dropped:0 overruns:0 frame:0
              TX packets:21173 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:372057 (372.0 KB)  TX bytes:13248977 (13.2 MB)

    vnet1     Link encap:Ethernet  HWaddr fe:54:00:9a:39:74  
              inet addr:192.168.23.1  Bcast:0.0.0.0          Mask:255.255.255.255
              inet6 addr: fe80::fc54:ff:fe9a:3974/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:7462 errors:0 dropped:0 overruns:0 frame:0
              TX packets:81072 errors:0 dropped:0 overruns:0         carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:3462349 (3.4 MB)  TX bytes:92936270 (92.9 MB)

Does anyone have some pointers, because i am lost?

Are you saying you have an nginx pod running on minikube and you want to access it externally? Or did I misunderstand the question? — Naim Salameh, Oct 05 '19 at 14:15
Do you want to expose the Nginx service through your system's public IP, to other systems on network? — Muralidharan.rade, Oct 10 '19 at 10:58

score 18 · Answer 1 · answered Nov 05 '19 at 14:04

18

Minikube doesn't support LoadBalancer services, so the service will never get an external IP.

But you can access the service anyway with its external port.

You can get the IP and PORT by running:

minikube service <service_name>

answered Nov 05 '19 at 14:04

Ezwig

400
1
3
14

This works only within cluster, not ourside – Abdul Apr 29 '21 at 05:05
3

But minikube does support `LoadBalancer` types of services? In conjunction with `minikube tunnel` isn't it? – Dmitry Kankalovich Sep 28 '21 at 16:24
https://minikube.sigs.k8s.io/docs/handbook/accessing/#loadbalancer-access – n1ghtm4n4g3r Feb 11 '23 at 11:17

score 9 · Answer 2 · answered Oct 11 '19 at 20:07

9

I assume you are using minikube in virtualbox (there was no info how do you start it and what is your host OS).

When you create a service with type=LoadBalancer you should also run minikube tunnel to expose LoadBalancers from cluster. Then when you run kubectl get svc you will get external IP of LoadBalancer. Still it's minikube's IP, so if you want to expose it externally from your machine you should put some reverseproxy or tunnel on your machine.

answered Oct 11 '19 at 20:07

Kamil

431
3
8

You are 100000% correct, its very confusing with minikube. I just created NodePort svc and have a nginx on the linux box where i installed minikube. After that its working. – Abdul Apr 30 '21 at 10:35
With this answer I found the minikube documentation for it: https://minikube.sigs.k8s.io/docs/handbook/accessing/#loadbalancer-access I did not think about looking there as I had the impression that this is an kubernetes internal problem. – Bluehorn Aug 05 '21 at 19:53

score 7 · Answer 3 · edited Jul 21 '22 at 14:42

7

If you're running Minikube on windows just run:

minikube tunnel

Note: It must be run in a separate terminal window to keep the tunnel open.

The above command will tunnel your container to localhost. then you can get your service URL by:

kubectl get services [service name]

replace [service name] with your service name. don't forget to add a mapped port on the external IP endpoint.

edited Jul 21 '22 at 14:42

Ojer_Dev

108
1
12

answered Feb 07 '21 at 09:48

Payam Khaninejad

7,692
6
45
55

Maheshvirus · Answer 4 · 2022-09-30T07:25:55.483

3

Minikube External IP :

minikube doesn’t allow to access the external IP`s directly for the service of a kind NodePort or LoadBalancer.

We don’t get the external IP to access the service on the local system. So the good option is to use minikube IP

Use the below command to get the minikube IP once your service is exposed.

minikube service service-name --url

Now use that URL to serve your purpose.

edited Sep 30 '22 at 07:25

answered Sep 28 '22 at 22:49

Maheshvirus

6,749
2
38
40

score 0 · Answer 5 · answered Jul 23 '20 at 15:55

0

TL;DR minikube has "addons" which you can use to handle ingress and load balancing. Just enable and configure one of those.

https://medium.com/faun/metallb-configuration-in-minikube-to-enable-kubernetes-service-of-type-loadbalancer-9559739787df

answered Jul 23 '20 at 15:55

Stephen

7,994
9
44
73

Kubernetes (Minikube) external ip does not work

5 Answers5

Linked