Kubernetes(Minikube)外部IP不起作用

本文介绍了Kubernetes(Minikube)外部IP不起作用的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我是Kubernetes的新手，我一直在浏览查找和阅读为什么我的外部IP无法解析.

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

我正在Ubuntu 16.04发行版上运行minikube.

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

当我在 192.168.42.165:32431/上获取http时，我得到了nginx页面.

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

服务的配置如下

# 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: {}

这些是我的ifconfog

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?

推荐答案

Minikube不支持LoadBalancer服务，因此该服务将永远不会获得外部IP.

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.

您可以通过运行以下命令获取IP和PORT:

You can get the IP and PORT by running:

minikube service <service_name>