amazon-web-services - Kube-up.sh在特定的AWS区域中永远循环

Question

尝试在AWS中设置新的Kubernetes集群时遇到非常奇怪的行为。

每当我尝试使用其默认配置运行kube-up.sh时，它都能完美运行，
群集及其所有相关组件的建立时间不到10分钟。

当我将“kube-aws-zone”设置为us-east-1e(与我当前的VPC相同)而不是us-west-2a(默认值)时，会出现问题。
安装过程陷入了循环，并显示以下消息:

Waiting 3 minutes for cluster to settle ..................Re-running salt highstate sudo: unable to resolve host ip-172-20-0-9 Waiting for cluster initialization.

This will continually check to see if the API for kubernetes is reachable. This might loop forever if there was some uncaught error during start up.

我试图在奴才中挖掘一点，然后在/ var / log / salt / minion中发现此错误

2015-10-01 14:52:54,912 [salt.loaded.int.module.cmdmod][ERROR ] Command 'runlevel /run/utmp' failed with return code: 1 2015-10-01 14:52:54,913 [salt.loaded.int.module.cmdmod][ERROR ] output: Too many arguments. 2015-10-01 14:53:00,902 [salt.state ][ERROR ] The named service kubelet is not available 2015-10-01 14:53:03,078 [salt.state ][ERROR ] The named service kube-proxy is not available 2015-10-01 14:53:16,677 [salt.state ][ERROR ] An exception occurred in this state: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/salt/state.py", line 1533, in call **cdata['kwargs']) File "/usr/lib/python2.7/dist-packages/salt/states/sysctl.py", line 56, in present configured = salt'sysctl.show' File "/usr/lib/python2.7/dist-packages/salt/modules/linux_sysctl.py", line 86, in show for line in salt.utils.fopen(config_file_path): File "/usr/lib/python2.7/dist-packages/salt/utils/init.py", line 1065, in fopen fhandle = open(*args, **kwargs) IOError: [Errno 2] No such file or directory: '/etc/sysctl.d/99-salt.conf'

2015-10-01 14:53:16,707 [salt.loaded.int.module.cmdmod][ERROR ] Command 'runlevel /run/utmp' failed with return code: 1 2015-10-01 14:53:16,708 [salt.loaded.int.module.cmdmod][ERROR ] output: Too many arguments. 2015-10-01 14:53:16,719 [salt.loaded.int.module.cmdmod][ERROR ] Command 'service docker status' failed with return code: 3 2015-10-01 14:53:16,719 [salt.loaded.int.module.cmdmod][ERROR ] output: * docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2015-10-01 14:53:16 UTC; 262ms ago Docs: http://docs.docker.com Process: 15285 ExecStart=/usr/bin/docker -d -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 15285 (code=exited, status=1/FAILURE)

Oct 01 14:53:16 ip-172-20-0-90 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE Oct 01 14:53:16 ip-172-20-0-90 systemd[1]: Unit docker.service entered failed state. Oct 01 14:53:16 ip-172-20-0-90 systemd[1]: docker.service failed. 2015-10-01 14:53:20,259 [salt.state ][ERROR ] The named service kubelet is not available 2015-10-01 14:53:20,687 [salt.state
][ERROR ] The named service kube-proxy is not available

我已尝试按照类似问题的建议删除并重新设置IAM角色，但最终没有运气。

将不胜感激。
谢谢，

Answer 1

该问题特定于us-east-1地区。
我必须编辑作为kube-up.sh的一部分创建的dhcp-set，并添加以下内容-

domain-name = ec2.internal

然后它像魅力一样工作。

更多信息-https://github.com/kubernetes/kubernetes/issues/7962#issuecomment-145324441