尽管资源看似可用,但无法启动新的 Pod

发布于 2025-01-09 23:09:15 字数 838 浏览 0 评论 0原文

尽管资源似乎可用,但我无法启动新的 Pod。

从下面的截图来看,应该有大约 40 个新 Pod 的空间。

输入图片这里的描述

而且从下面的屏幕截图来看,节点似乎没有得到充分利用

在此处输入图像描述

但是,我目前面临以下错误消息

0/3 nodes are available: 1 Insufficient cpu, 2 node(s) had volume node affinity conflict.

如下

0/3 nodes are available: 1 Too many pods, 2 node(s) had volume node affinity conflict.

昨晚,我的大部分内容 服务需要很少的内存和CPU。因此,它们的资源配置如下所示

resources:
  limits:
    cpu: 100m
    memory: 64Mi
  requests:
    cpu: 100m
    memory: 32Mi

为什么我无法部署更多 Pod?以及如何解决这个问题?

I'm unable to launch new pods despite resources seemingly being available.

Judging from the below screenshot there should be room for about 40 new pods.

enter image description here

And also judging from the following screenshot the nodes seems fairly underutilized

enter image description here

However I'm currently facing the below error message

0/3 nodes are available: 1 Insufficient cpu, 2 node(s) had volume node affinity conflict.

And last night it was the following

0/3 nodes are available: 1 Too many pods, 2 node(s) had volume node affinity conflict.

Most of my services require very little memory and cpu. And therefore their resources are configured as seen below

resources:
  limits:
    cpu: 100m
    memory: 64Mi
  requests:
    cpu: 100m
    memory: 32Mi

Why I can't deploy more pods? And how to fix this?

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

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

发布评论

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

评论(2

蓝天 2025-01-16 23:09:15

您的问题是“卷节点亲和力冲突”。

来自 Kubernetes Pod 警告:1 个节点存在卷节点关联性冲突

当持久卷声明 Pod 正在使用的持久卷被调度到不同的可用区(而不是一个可用区)时,就会出现“卷节点亲和性冲突”错误,因此实际的 Pod 由于无法连接到而无法被调度来自另一个区域的音量。

首先,尝试准确调查问题出在哪里。您可以在此处找到详细指南。您将需要如下命令:

kubectl get pv  
kubectl describe pv  
kubectl get pvc  
kubectl describe pvc

然后您可以删除 PV 和 PVC,并将 pod 与 PV 和 PVC 一起移动到同一区域。

Your problem is "volume node affinity conflict".

From Kubernetes Pod Warning: 1 node(s) had volume node affinity conflict:

The error "volume node affinity conflict" happens when the persistent volume claims that the pod is using are scheduled on different zones, rather than on one zone, and so the actual pod was not able to be scheduled because it cannot connect to the volume from another zone.

First, try to investigate exactly where the problem is. You can find a detailed guide here. You will need commands like:

kubectl get pv  
kubectl describe pv  
kubectl get pvc  
kubectl describe pvc

Then you can delete the PV and PVC and move pods to the same zone along with the PV and PVC.

还如梦归 2025-01-16 23:09:15

卷节点关联冲突 - 您尝试挂载的卷在任何节点上都不可用。您可以解决此问题或将您的 volumes 部分粘贴到问题中以进行进一步检查。

volume node affinity conflict - the volume you tried to mount is not available on any of the node. You can resolve this or paste your volumes section to the question for further examination.

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