Kubernetes安装与流浪＆CoreOS背后代理

我是代理服务器的后面，并继“Kubernetes安装与流浪& CoreOS”这里列出的步骤：https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant.html Kubernetes安装与流浪＆CoreOS背后代理

敲定安装后，当我运行

$ kubectl get nodes

我得到错误。

Unable to connect to the server: Service Unavailable

e1，c1和w1都启动了，我可以发出$ vagrant ssh每个。

当我检查w1时，我看到码头服务没有运行，下面列出的错误。

---------------------------------------------------------------------------- 
-- Unit docker.service has failed. 
-- 
-- The result is dependency. 
Aug 19 04:09:25 w1 systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'. 
Aug 19 04:09:25 w1 systemd[1]: flanneld.service: Unit entered failed state. 
Aug 19 04:09:25 w1 systemd[1]: flanneld.service: Failed with result 'exit-code'. 
Aug 19 04:09:30 w1 systemd[1]: flanneld.service: Service hold-off time over, scheduling restart. 
Aug 19 04:09:30 w1 systemd[1]: Stopped Network fabric for containers. 
-- Subject: Unit flanneld.service has finished shutting down 
-- Defined-By: systemd 
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- Unit flanneld.service has finished shutting down. 
Aug 19 04:09:30 w1 systemd[1]: Starting Network fabric for containers... 
-- Subject: Unit flanneld.service has begun start-up 
-- Defined-By: systemd 
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- Unit flanneld.service has begun starting up. 
Aug 19 04:09:30 w1 rkt[6888]: image: using image from file /usr/lib/rkt/stage1-images/stage1-fly.aci 
Aug 19 04:09:31 w1 rkt[6888]: image: searching for app image quay.io/coreos/flannel 
Aug 19 04:09:31 w1 rkt[6888]: run: discovery failed 
Aug 19 04:09:31 w1 systemd[1]: flanneld.service: Main process exited, code=exited, status=1/FAILURE 
Aug 19 04:09:31 w1 systemd[1]: Failed to start Network fabric for containers. 
-- Subject: Unit flanneld.service has failed 
-- Defined-By: systemd 
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 
-- 
-- Unit flanneld.service has failed. 
-- 
-- The result is failed. 
Aug 19 04:09:31 w1 systemd[1]: flanneld.service: Unit entered failed state. 
Aug 19 04:09:31 w1 systemd[1]: flanneld.service: Failed with result 'exit-code'. 

----------------------------------------------------------------------------

我猜这个问题是因为我在代理的背后。运行安装步骤之前我发出命令

$export "HTTP_PROXY=http://http-proxy.xxxxxx.com:8080" 
$export "HTTPS_PROXY=http://http-proxy.xxxxxx.com:8080" 
$export "http_proxy=http://http-proxy.xxxxxx.com:8080" 
$export "https_proxy=http://http-proxy.xxxxxx.com:8080"

你还是知道这是足以让后面的代理安装，我需要代理设置添加到别的地方去。

谢谢你在前进， turgos

来源

2016-08-19 turgos

要导出的变量只是在当前的shell会话是有效的，他们不提供给您的绒布systemd单元。

创建下面的下拉式的systemd单元目录中，然后用systemctl daemon-reload重载守护进程，它应该绒布解决您的问题：

/etc/systemd/system/flannel.service.d/proxy.conf：

[Service] 
Environment="HTTP_PROXY=http://http-proxy.xxx:8080" 
Environment="...

一个类似的例子可在CoreOS文档中：Customizing Docker

来源

2016-08-20 07:55:36

是的，这有助于解决法兰绒问题，我可以看到在所有3台机器上运行的Docker e1，c1和w1。但是当我进行“$ kubectl get nodes”调用时，我仍然收到“Unable to connect to the server：Service Unavailable”回复。是否有任何Kubernetes日志用于诊断问题？ – turgos

这取决于你的API服务器是如何启动的，也是一个systemd单元？在这种情况下，试试'journalctl -u kube-apiserver'。在容器内（rkt，Docker）？然后只需检查该特定容器的日志。 –

如果您的kubernetes组件在rkt容器内运行（这似乎是您的设置中的情况），此文档页面可能会对您有所帮助：https://coreos.com/rkt/docs/latest/commands.html#logging –

Kubernetes安装与流浪＆CoreOS背后代理

回答

相关问题