首页 > 解决方案 > 无法远程登录 kube-proxy 暴露的 localhost 端口

问题描述

我有一个 k8s 集群,并且有一些端口被 kube-proxy 暴露,例如 31381 和 31382。

[root@rg1-ostack219 leo]# hostname -I | awk '{print $1}'
10.211.85.97
[root@rg1-ostack219 leo]# netstat -anp |grep " LISTEN "
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      21156/sshd
tcp        0      0 127.0.0.1:10009         0.0.0.0:*               LISTEN      90833/scribed
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      3006/master
tcp        0      0 0.0.0.0:16509           0.0.0.0:*               LISTEN      2207/libvirtd
tcp        0      0 127.0.0.1:33123         0.0.0.0:*               LISTEN      89258/kubelet
tcp        0      0 127.0.0.1:10248         0.0.0.0:*               LISTEN      89258/kubelet
tcp        0      0 0.0.0.0:52360           0.0.0.0:*               LISTEN      2464/hooagent
tcp        0      0 127.0.0.1:10249         0.0.0.0:*               LISTEN      64755/kube-proxy
tcp        0      0 0.0.0.0:6666            0.0.0.0:*               LISTEN      97587/ssh
tcp        0      0 127.0.0.1:10251         0.0.0.0:*               LISTEN      90172/kube-schedule
tcp        0      0 127.0.0.1:2379          0.0.0.0:*               LISTEN      90052/etcd
tcp        0      0 10.211.85.97:2379       0.0.0.0:*               LISTEN      90052/etcd
tcp        0      0 127.0.0.1:10252         0.0.0.0:*               LISTEN      89938/kube-controll
tcp        0      0 10.211.85.97:2380       0.0.0.0:*               LISTEN      90052/etcd
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      1675/rpcbind
tcp6       1      0 :::31381                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31413                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31382                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31830                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::22                   :::*                    LISTEN      21156/sshd
tcp6       0      0 :::32026                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::443                  :::*                    LISTEN      91307/traefik
tcp6       0      0 :::32541                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31485                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31390                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31392                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::30692                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::31400                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::6666                 :::*                    LISTEN      97587/ssh
tcp6       0      0 :::10250                :::*                    LISTEN      89258/kubelet
tcp6       0      0 :::6443                 :::*                    LISTEN      89836/kube-apiserve
tcp6       0      0 :::9100                 :::*                    LISTEN      50266/node_exporter
tcp6       0      0 :::111                  :::*                    LISTEN      1675/rpcbind
tcp6       0      0 :::8080                 :::*                    LISTEN      91307/traefik
tcp6       0      0 :::80                   :::*                    LISTEN      91307/traefik
tcp6       0      0 :::10256                :::*                    LISTEN      64755/kube-proxy
tcp6       0      0 :::10257                :::*                    LISTEN      89938/kube-controll
tcp6       0      0 :::32116                :::*                    LISTEN      64755/kube-proxy
tcp6       1      0 :::31380                :::*                    LISTEN      64755/kube-proxy

问题是当我运行时telnet 10.211.85.97 31381telnet 127.0.0.1 6443一切正常,但是当我运行时telnet 127.0.0.1 31381,没有任何响应。

标签: linuxkubernetestelnet

解决方案


它不会在连接到您的管理程序主机的同一本地主机上进行侦听。每个 kube-proxy 服务代理都有自己的集群 IP,其功能或多或少类似于容器,但通常具有更多的 iptables 魔法。


推荐阅读