我们有3个节点的k8s集群。 我可以通过奴隶公共IP& amp; NodePort。尽管有实际的pod位置,它仍然适用于每个奴隶。但由于某种原因,它不适合主人。
主节点上的kubectl get services --all-namespaces
打印实际服务列表:
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
xxx kibana NodePort 10.100.214.218 <none> 5601:30141/TCP 1d
如何为主节点启用此类路由?
Kubernetes版本:v1.8.6
kubectl get pods -o wide --all-namespaces
的基础设施相关输出:
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
kube-system etcd-k8s-master 1/1 Running 9 2d 172.20.41.199 k8s-master
kube-system kube-apiserver-k8s-master 1/1 Running 1 2d 172.20.41.199 k8s-master
kube-system kube-controller-manager-k8s-master 1/1 Running 1 2d 172.20.41.199 k8s-master
kube-system kube-dns-545bc4bfd4-2fq94 3/3 Running 0 2d 10.36.0.14 k8s-slave2
kube-system kube-proxy-dhsl9 1/1 Running 1 2d 172.20.41.199 k8s-master
kube-system kube-proxy-mkjzn 1/1 Running 0 2d 172.20.41.194 k8s-slave1
kube-system kube-proxy-stjm6 1/1 Running 1 2d 172.20.41.195 k8s-slave2
kube-system kube-scheduler-k8s-master 1/1 Running 9 2d 172.20.41.199 k8s-master
kube-system kubernetes-dashboard-747d579ff5-qp7rh 1/1 Running 2 2d 10.32.0.2 k8s-master
kube-system weave-net-n8n64 2/2 Running 0 2d 172.20.41.194 k8s-slave1
kube-system weave-net-vh6ng 2/2 Running 1 2d 172.20.41.195 k8s-slave2
kube-system weave-net-w9mn8 2/2 Running 2 2d 172.20.41.199 k8s-master