search

alibaba / kt-connect

A toolkit for Integrating with your kubernetes dev environment more efficiently
https://alibaba.github.io/kt-connect/#/
GNU General Public License v3.0
1.48k stars 230 forks source link

ktctl connect命令连接k8s集群，会添加额外的路由规则导致原本的服务访问不了 #437

Open liqiao7 opened 12 months ago

liqiao7 commented 12 months ago

1688547910619

环境描述： 134.160.180.70 haproxy+keepalived搭建的虚拟ip 134.160.180.71 master1 134.160.180.72 master2 134.160.180.73 master3 134.160.180.74 node1 134.160.180.75 node2 134.160.180.76 node3 134.160.180.80 gitlab

问题描述： 如果所示，使用命令ktctl connect --kubeconfig ./70kubeconfig连接k8s集群时，会输出如下日志

5:03PM INF Adding route to 134.160.180.128/25 5:03PM INF Adding route to 134.160.180.0/26 5:03PM INF Adding route to 134.160.180.96/27 5:03PM INF Adding route to 134.160.180.80/28 5:03PM INF Adding route to 134.160.180.72/29 5:03PM INF Adding route to 134.160.180.64/30 5:03PM INF Adding route to 134.160.180.68/31 5:03PM INF Adding route to 134.160.180.71/32

其中134.160.180.80为另外一台服务器（部署了gitlab）的地址，使用ktctl连接成功后，无法访问该gitlab，可以ping通134.160.180.80这个ip，但是访问gitlab会出现404错误，关闭ktctl后，一切正常。

貌似是因为这个ip被路由到别的地方去了，这个是在哪可以进行配置吗？或者说有办法不让这个ip添加到路由当中吗？

wangxiaodao1990 commented 11 months ago

解决了？

liqiao7 commented 11 months ago

解决了？

目前还没有呢，用gitlab时就把ktctl给关了

dayu521 commented 11 months ago

ktctl connect --kubeconfig ./70kubeconfig --excludeIps 134.160.180.80/28

在后面加上这个应该就好了

yearnxiao commented 10 months ago

这是什么牛逼公司，集群所有节点都用公网IP连接通讯

liqiao7 commented 10 months ago

这是什么牛逼公司，集群所有节点都用公网IP连接通讯

这是我们的内网ip