The goal for setting up the kubernetes kube-proxy on another EC2 instance would be for the network configuration (iptables) to propagate there. So that instance would not be a minion and could take requests from internet and because of its kube-proxy managed iptables, the requests would be forwarded to correct kubernetes services.
在另一个EC2实例上设置kubernetes kube-proxy的目标是在那里传播网络配置(iptables)。因此,该实例不会是一个小兵并且可以接受来自互联网的请求,并且由于其kube-proxy托管的iptables,请求将被转发到正确的kubernetes服务。
1 个解决方案
#1
Option 1: Install an extra node in your cluster and then go in and remove the kubelet from the extra node (if you are using salt you should be able to reconfigure the salt to not include the kubelet). This will leave you with a kube-proxy that is configured with the location of the master and that is babysat by monit.
选项1:在群集中安装一个额外的节点,然后进入并从额外节点中删除kubelet(如果使用salt,则应该能够重新配置盐以不包括kubelet)。这将为您提供一个kube-proxy,它配置了master的位置,并且是monit的babysat。
Option 2: Download just the kube-proxy binary and run it manually. You should be able to look at the command line arguments it's been passed on one of the nodes in your cluster and clone them. Remember to run it as root.
选项2:仅下载kube-proxy二进制文件并手动运行。您应该能够查看它在集群中某个节点上传递的命令行参数并克隆它们。记得以root身份运行它。
#1
Option 1: Install an extra node in your cluster and then go in and remove the kubelet from the extra node (if you are using salt you should be able to reconfigure the salt to not include the kubelet). This will leave you with a kube-proxy that is configured with the location of the master and that is babysat by monit.
选项1:在群集中安装一个额外的节点,然后进入并从额外节点中删除kubelet(如果使用salt,则应该能够重新配置盐以不包括kubelet)。这将为您提供一个kube-proxy,它配置了master的位置,并且是monit的babysat。
Option 2: Download just the kube-proxy binary and run it manually. You should be able to look at the command line arguments it's been passed on one of the nodes in your cluster and clone them. Remember to run it as root.
选项2:仅下载kube-proxy二进制文件并手动运行。您应该能够查看它在集群中某个节点上传递的命令行参数并克隆它们。记得以root身份运行它。