这是一个创建于 2530 天前的主题，其中的信息可能已经有所发展或是发生改变。
问题
按 github 上操作来的
kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml Service 的 type 我改成了 NodePort,端口用了30001,pod 也跑起来了
root@k8s-spider-master1:~# kubectl -n kube-system get po NAME READY STATUS RESTARTS AGE calico-node-fvcm5 2/2 Running 0 12d calico-node-m4msr 2/2 Running 0 22d calico-node-xmfhk 2/2 Running 0 12d coredns-8686dcc4fd-lg9wf 1/1 Running 0 22d coredns-8686dcc4fd-sc2v4 1/1 Running 0 22d etcd-k8s-spider-master1 1/1 Running 0 22d kube-apiserver-k8s-spider-master1 1/1 Running 0 22d kube-controller-manager-k8s-spider-master1 1/1 Running 0 22d kube-proxy-9l89z 1/1 Running 0 12d kube-proxy-bcrs6 1/1 Running 0 12d kube-proxy-sgq8z 1/1 Running 0 22d kube-scheduler-k8s-spider-master1 1/1 Running 0 22d kubernetes-dashboard-69fdd5c8dd-vhcgz 1/1 Running 0 24m tiller-deploy-c7978c846-jtc8s 1/1 Running 0 7d1h 但是访问curl https://172.16.140.22:30001或者curl http://172.16.140.22:30001 一直没响应
 | 1 mritd 2019 年 5 月 22 日 via iPhone 检查一下 IPTABLES FORWARD 链，docker 重启可能会禁用 |
 | 2 RalphHuang 2019 年 5 月 22 日 iptables -P FORWARD ACCEPT |
Select Language