gpt4 book ai didi

kubernetes - stackdriver-metadata-agent-cluster级别由于[2a00:1450:400c:c09::5f]:443导致很多失败:I/O超时

转载 作者:行者123 更新时间:2023-12-02 12:28:15 25 4
gpt4 key购买 nike

我在Europe-west1-d区域中拥有 1.14.10-gke.27 k8s

在过去的几天里,我在kube-system ns中有很多stackdriver-metadata-agent-cluster-level pod重新启动,但有错误

I0402 16:39:12.688053       1 main.go:142] All resources are being watched, agent has started successfully
I0402 16:39:12.688108 1 main.go:145] No statusz port provided; not starting a server
I0402 16:39:29.383562 1 retry.go:80] call failed with err=rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp [2a00:1450:400c:c09::5f]:443: i/o timeout", retrying.
I0402 16:39:29.383667 1 retry.go:80] call failed with err=rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp [2a00:1450:400c:c09::5f]:443: i/o timeout", retrying.
I0402 16:39:30.483072 1 retry.go:80] call failed with err=rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp [2a00:1450:400c:c09::5f]:443: i/o timeout", retrying.
I0402 16:39:30.783091 1 retry.go:80] call failed with err=rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp [2a00:1450:400c:c09::5f]:443: i/o timeout", retrying.
I0402 16:40:09.186357 1 binarylog.go:265] rpc: flushed binary log to ""
I0402 16:41:29.383025 1 binarylog.go:265] rpc: flushed binary log to ""

logs screenshot

这是Google网路问题吗?

最佳答案

我将其添加为答案,因为如果我在注释中添加了很多代码,它们将完全不可读。一旦我们设法找出解决方案,我将对其进行编辑。

您能否运行这些 Stackdriver日志查询,并将输出作为代码示例发布到您的问题中(在所选文本上使用ctrl + k)?

resource.type="k8s_container"
resource.labels.project_id="<project_id>"
resource.labels.location="<location e.g. us-central1-c>"
resource.labels.cluster_name="<cluster-name>"
resource.labels.namespace_name="kube-system"
labels.k8s-pod/app="stackdriver-metadata-agent"
labels.k8s-pod/cluster-level="true"
"oom"

resource.type="k8s_container"
resource.labels.project_id="<project-id>"
resource.labels.location="<location e.g. us-central1-c>"
resource.labels.cluster_name="<cluster-name>"
resource.labels.namespace_name="kube-system"
labels.k8s-pod/app="stackdriver-metadata-agent"
labels.k8s-pod/cluster-level="true"
severity>=WARNING
sourceLocation.file!="reflector.go"

请不要将其作为屏幕截图,因为它在搜索时是完全没有用的。

关于kubernetes - stackdriver-metadata-agent-cluster级别由于[2a00:1450:400c:c09::5f]:443导致很多失败:I/O超时,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/60999154/

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