AWS EKS - 只能启动 2 个 Pod - 太多 Pod 错误 [英] AWS EKS - Only 2 pod can be launched - Too many pods error

问题描述

根据这个文章 和命令 kubectl get nodes -o yaml |grep pods 输出.

Each t2.micro node should be able to run 4 pods according to this article and the command kubectl get nodes -o yaml | grep pods output.

但我有两个节点，我只能启动 2 个 Pod.3rd pod 卡住了以下错误消息.

But I have two nodes and I can launch only 2 pods. 3rd pod gets stuck with the following error message.

会不会是应用程序使用了太多资源而导致无法启动更多 Pod?如果是这种情况，则可能表明CPU 或内存不足.

Could it be the application using too much resource and as a result its not launching more pods? If that was the case it could indicate Insufficient CPU or memory.

Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  33s (x2 over 33s)  default-scheduler  0/2 nodes are available: 2 Too many pods.

推荐答案

根据 AWS 文档 每个实例类型每个网络接口的 IP 地址 t2.micro 只有 2 网络接口和 2 IPv4 地址每个接口.所以你是对的，只有 4 个 IP 地址.

According to the AWS documentation IP addresses per network interface per instance type the t2.micro only has 2 Network Interfaces and 2 IPv4 addresses per interface. So you are right, only 4 IP addresses.

但是 EKS 部署了 DaemonSets 例如CoreDNS 和 kube-proxy，因此每个节点上的一些 IP 地址已经分配.

But EKS deploys DaemonSets for e.g. CoreDNS and kube-proxy, so some IP addresses on each node is already allocated.

这篇关于AWS EKS - 只能启动 2 个 Pod - 太多 Pod 错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！