牧场主 - 无法创建POD SANDBOX:RPC错误:代码=未知DESC

发布于 2025-01-25 03:03:56 字数 461 浏览 2 评论 0原文

有人知道如何解决此错误消息吗? 同一牧场容器的工作正常,直到大约2周。

无法创建POD SANDBOX:RPC错误:代码=未知desc = [无法设置沙盒容器“ E85E08BF70BFBFBB8CAFE4B61B79F47008B4E829310600E5, CNI无法设置POD“ YKGWAGG-845B559FBF-CLRP8_AGG”网络:获取簇状信息:连接未经授权:未经授权,无法清理沙盒容器“ E85E08BF70BFBFBB8CAFE4B61B61B79F47008B4E829310600EM在CNI中未能拆除pod“ ykgwagg-845b559fbf-clrp8_agg”网络:错误获取簇状信息:连接未经授权:未授权]

enter Image Description

Does any one know how to resolve this error message?
The same Rancher container's were working just fine until about 2 weeks.

Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "e85e08bf70bfbb8cafe4b61b79f47008b4e829310600e5defb29f0a6600d25e3" network for pod "ykgwagg-845b559fbf-clrp8": networkPlugin cni failed to set up pod "ykgwagg-845b559fbf-clrp8_agg" network: error getting ClusterInformation: connection is unauthorized: Unauthorized, failed to clean up sandbox container "e85e08bf70bfbb8cafe4b61b79f47008b4e829310600e5defb29f0a6600d25e3" network for pod "ykgwagg-845b559fbf-clrp8": networkPlugin cni failed to teardown pod "ykgwagg-845b559fbf-clrp8_agg" network: error getting ClusterInformation: connection is unauthorized: Unauthorized]

enter image description here

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

清君侧 2025-02-01 03:03:56

当我在POD中遇到错误消息时,如下所述:

error getting ClusterInformation: connection is unauthorized: Unauthorized

此错误指示了RKE2运河网络设置中的令牌到期问题,从而导致无法创建新POD的情况。

为了更新令牌并还原普通的POD创建功能,我执行了以下命令:

kubectl rollout restart ds/rke2-canal -n kube-system

此命令将重新启动Kube-System名称空间内的RKE2 Canal Daemonset Pods。

重新启动POD后,确保通过创建新的POD或验证现有POD现在可以成功创建现有POD来确保解决令牌续订问题。

When I was encountering the error message in a pod describe like the following:

error getting ClusterInformation: connection is unauthorized: Unauthorized

This error is indicative of token expiration issues within the RKE2 canal network setup, leading to a situation where new pods cannot be created.

To renew the token and restore normal pod creation functionality, I have executed the following command:

kubectl rollout restart ds/rke2-canal -n kube-system

This command will restart the RKE2 canal DaemonSet pods within the kube-system namespace.

After restarting the pods, ensure that the token renewal issue is resolved by creating a new pod or verifying that existing pods can now be created successfully.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文