gpt4 book ai didi

kubernetes - Calico 等待 etcd 报错 Kubespray

转载 作者:行者123 更新时间:2023-12-04 17:50:42 28 4
gpt4 key购买 nike

尝试使用 Kubespray 在 EC2 集群上安装 Kubernetes 时出现以下错误

TASK [network_plugin/calico : Calico | wait for etcd] ***********************************************************************************************************************************************************************************************
Thursday 20 July 2017 17:21:40 -0400 (0:00:00.327) 0:04:16.018 *********
FAILED - RETRYING: Calico | wait for etcd (10 retries left).
FAILED - RETRYING: Calico | wait for etcd (9 retries left).
FAILED - RETRYING: Calico | wait for etcd (8 retries left).
FAILED - RETRYING: Calico | wait for etcd (7 retries left).
FAILED - RETRYING: Calico | wait for etcd (6 retries left).
FAILED - RETRYING: Calico | wait for etcd (5 retries left).
FAILED - RETRYING: Calico | wait for etcd (4 retries left).
FAILED - RETRYING: Calico | wait for etcd (3 retries left).
FAILED - RETRYING: Calico | wait for etcd (2 retries left).
FAILED - RETRYING: Calico | wait for etcd (1 retries left).
fatal: [node1 -> None]: FAILED! => {"attempts": 10, "changed": false, "content": "", "failed": true, "msg": "Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "https://localhost:2379/health"}

有人知道这是为什么吗?这是我提交的 Github 问题,其中包含更多信息 https://github.com/kubernetes-incubator/kubespray/issues/1466

最佳答案

TLDR;同时打开 2379 和 2380 端口

我遇到了同样的问题,发现我需要为 etcd 打开两个端口。明显的端口是 2379,因为它在 ansible 错误消息中。当我检查其中一个故障节点上 etcd 容器的日志时,我发现它正在尝试与端口 2380 上的其他 etcd 节点通信。我更新了我的安全组以允许两个端口上的流量并且此错误已解决。

关于kubernetes - Calico 等待 etcd 报错 Kubespray,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/45225754/

28 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com