We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
calico网络使用daemonset部署之后,如果master主机不加入node集群中,master上是不会运行calico-node的,没有运行calico那么master就没有到node中pod的路由,那么dashboard通过master的ip是无法访问kube-dashboard的,需要单独在master上起一个calico进程,保证master和node之间的路由和通信,有什么好的方法解决
The text was updated successfully, but these errors were encountered:
上周就解决了,请看更新说明。 1.只能在master上也部署kubelet和kube-proxy,然后使用 kubectl cordon 禁止普通pod调度到master; 2.或者就索性master上不装calico,如果只是为了访问dashboard,可以用NodePort方式,新版dashboard本身自带安全登陆特性,不一定要通过 apiserver去访问
Sorry, something went wrong.
同 ISSUE #130
No branches or pull requests
calico网络使用daemonset部署之后,如果master主机不加入node集群中,master上是不会运行calico-node的,没有运行calico那么master就没有到node中pod的路由,那么dashboard通过master的ip是无法访问kube-dashboard的,需要单独在master上起一个calico进程,保证master和node之间的路由和通信,有什么好的方法解决
The text was updated successfully, but these errors were encountered: