Kubernetes 无法在EKS中的ManagedNodeGroup上部署POD

Kubernetes 无法在EKS中的ManagedNodeGroup上部署POD,kubernetes,Kubernetes,我正在EKS中使用托管节点组尝试集群。我能够将CSI连接到集群,并能够创建storageClass和persistentVolumeClaim,但当我尝试部署部署时。POD似乎未与指定的节点关联 吊舱文件 apiVersion: apps/v1 kind: Deployment metadata: name: voldeployment labels: app: my-app spec: replicas: 2 strategy: type: Recreate

我正在EKS中使用托管节点组尝试集群。我能够将CSI连接到集群,并能够创建storageClass和persistentVolumeClaim,但当我尝试部署部署时。POD似乎未与指定的节点关联

吊舱文件

apiVersion: apps/v1
kind: Deployment
metadata:
  name: voldeployment
  labels:
    app: my-app
spec:
  replicas: 2
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: my-app
  template:
    metadata:
      labels:
        app: my-app
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                - key: role
                  operator: In
                  values:
                    - general
                - key: disktype
                  operator: In
                  values:
                    - ssd
                - key: alpha.eksctl.io/nodegroup-name
                  operator: Exists
      containers:
        - name: ubuntu-ctr
          image: ubuntu:latest
          command:
          - /bin/bash
这就是豆荚的样子

Name:           voldeployment-695bb94474-d6ptq
Namespace:      default
Priority:       0
Node:           <none>
Labels:         app=my-app
                pod-template-hash=695bb94474
Annotations:    kubernetes.io/psp: eks.privileged
Status:         Pending
IP:             
IPs:            <none>
Controlled By:  ReplicaSet/voldeployment-695bb94474
Containers:
  ubuntu-ctr:
    Image:      ubuntu:latest
    Port:       <none>
    Host Port:  <none>
    Command:
      /bin/bash
      -c
      sleep 60m
    Environment:  <none>
    Mounts:
      /data from data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-xskpn (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  pvc1
    ReadOnly:   false
  default-token-xskpn:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-xskpn
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  73s (x4 over 4m12s)  default-scheduler  0/2 nodes are available: 2 Too many pods.
名称:voldeployment-695bb94474-d6ptq
名称空间:默认值
优先级:0
节点:
标签:app=我的app
pod模板哈希=695bb94474
注释:kubernetes.io/psp:eks.privileged
状态:待定
知识产权:
IPs:
控制人:ReplicaSet/voldeployment-695bb94474
容器:
ubuntu ctr:
图片:ubuntu:最新版本
端口:
主机端口:
命令:
/bin/bash
-c
睡眠60米
环境:
挂载:
/来自数据的数据(rw)
/来自默认令牌xskpn(ro)的var/run/secrets/kubernetes.io/serviceCount
条件:
类型状态
播客计划错误
卷数:
数据:
类型:PersistentVolumeClaim(对同一命名空间中PersistentVolumeClaim的引用)
权利要求书名称:pvc1
只读:false
默认令牌xskpn:
类型:Secret(由Secret填充的卷)
SecretName:默认令牌xskpn
可选:false
QoS等级:最佳努力
节点选择器:
容差:node.kubernetes.io/未就绪:NoExecute op=存在300秒
node.kubernetes.io/unreachable:NoExecute op=存在300秒
活动:
从消息中键入原因年龄
----     ------            ----                 ----               -------
警告失败调度73s(x4超过4m12s)默认调度程序0/2节点可用:2个POD过多。
节点看起来像这样

Name:               ip-192-168-100-146.ec2.internal
Roles:              <none>
Labels:             alpha.eksctl.io/cluster-name=Example-cluster
                    alpha.eksctl.io/nodegroup-name=managed-ng-1
                    beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/instance-type=t2.micro
                    beta.kubernetes.io/os=linux
                    eks.amazonaws.com/capacityType=ON_DEMAND
                    eks.amazonaws.com/nodegroup=managed-ng-1
                    eks.amazonaws.com/nodegroup-image=ami-090a8b0372a148572
                    eks.amazonaws.com/sourceLaunchTemplateId=lt-01a95a53f5379e6c6
                    eks.amazonaws.com/sourceLaunchTemplateVersion=1
                    failure-domain.beta.kubernetes.io/region=us-east-1
                    failure-domain.beta.kubernetes.io/zone=us-east-1f
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=ip-192-168-100-146.ec2.internal
                    kubernetes.io/os=linux
                    node.kubernetes.io/instance-type=t2.micro
                    role=general
                    topology.ebs.csi.aws.com/zone=us-east-1f
                    topology.kubernetes.io/region=us-east-1
                    topology.kubernetes.io/zone=us-east-1f
Annotations:        csi.volume.kubernetes.io/nodeid: {"ebs.csi.aws.com":"i-0b551804ff7079b95"}
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Mon, 08 Feb 2021 16:02:14 +0530
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  ip-192-168-100-146.ec2.internal
  AcquireTime:     <unset>
  RenewTime:       Mon, 08 Feb 2021 17:08:07 +0530
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Mon, 08 Feb 2021 17:05:26 +0530   Mon, 08 Feb 2021 16:02:13 +0530   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Mon, 08 Feb 2021 17:05:26 +0530   Mon, 08 Feb 2021 16:02:13 +0530   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Mon, 08 Feb 2021 17:05:26 +0530   Mon, 08 Feb 2021 16:02:13 +0530   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            True    Mon, 08 Feb 2021 17:05:26 +0530   Mon, 08 Feb 2021 16:02:44 +0530   KubeletReady                 kubelet is posting ready status
Addresses:
  InternalIP:   192.168.100.146
  Hostname:     ip-192-168-100-146.ec2.internal
  InternalDNS:  ip-192-168-100-146.ec2.internal
Capacity:
  attachable-volumes-aws-ebs:  39
  cpu:                         1
  ephemeral-storage:           8376300Ki
  hugepages-2Mi:               0
  memory:                      1006900Ki
  pods:                        4
Allocatable:
  attachable-volumes-aws-ebs:  39
  cpu:                         940m
  ephemeral-storage:           6645856244
  hugepages-2Mi:               0
  memory:                      598324Ki
  pods:                        4
System Info:
  Machine ID:                 4ec92546167f44ed87b3bccf78d597bb
  System UUID:                EC247791-4550-81B2-5CE7-0B5ACD5E96C5
  Boot ID:                    15d14b07-6e8e-48ad-9e6f-71225d16ea3c
  Kernel Version:             4.14.209-160.339.amzn2.x86_64
  OS Image:                   Amazon Linux 2
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  docker://19.3.6
  Kubelet Version:            v1.18.9-eks-d1db3c
  Kube-Proxy Version:         v1.18.9-eks-d1db3c
ProviderID:                   aws:///us-east-1f/i-0b551804ff7079b95
Non-terminated Pods:          (4 in total)
  Namespace                   Name                       CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                   ----                       ------------  ----------  ---------------  -------------  ---
  kube-system                 aws-node-8vv8q             10m (1%)      0 (0%)      0 (0%)           0 (0%)         66m
  kube-system                 coredns-c79dcb98c-nk4vv    100m (10%)    0 (0%)      70Mi (11%)       170Mi (29%)    71m
  kube-system                 ebs-csi-node-x87sv         0 (0%)        0 (0%)      0 (0%)           0 (0%)         63m
  kube-system                 kube-proxy-2fp4k           100m (10%)    0 (0%)      0 (0%)           0 (0%)         66m
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource                    Requests    Limits
  --------                    --------    ------
  cpu                         210m (22%)  0 (0%)
  memory                      70Mi (11%)  170Mi (29%)
  ephemeral-storage           0 (0%)      0 (0%)
  hugepages-2Mi               0 (0%)      0 (0%)
  attachable-volumes-aws-ebs  0           0
Events:                       <none>
名称:ip-192-168-100-146.ec2.internal
角色:
标签:alpha.eksctl.io/cluster name=示例集群
alpha.eksctl.io/nodegroup name=managed-ng-1
beta.kubernetes.io/arch=amd64
beta.kubernetes.io/实例类型=t2.micro
beta.kubernetes.io/os=linux
eks.amazonaws.com/capacityType=随需应变
eks.amazonaws.com/nodegroup=managed-ng-1
eks.amazonaws.com/nodegroup image=ami-090a8b0372a148572
eks.amazonaws.com/sourceLaunchTemplateId=lt-01a95a53f5379e6c6
eks.amazonaws.com/sourceLaunchTemplateVersion=1
故障域.beta.kubernetes.io/region=us-east-1
故障域.beta.kubernetes.io/zone=us-east-1f
kubernetes.io/arch=amd64
kubernetes.io/hostname=ip-192-168-100-146.ec2.internal
kubernetes.io/os=linux
node.kubernetes.io/实例类型=t2.micro
角色=一般
topology.ebs.csi.aws.com/zone=us-east-1f
topology.kubernetes.io/region=us-east-1
拓扑结构.kubernetes.io/zone=us-east-1f
注释:csi.volume.kubernetes.io/nodeid:{“ebs.csi.aws.com”:“i-0b551804ff7079b95”}
node.alpha.kubernetes.io/ttl:0
volumes.kubernetes.io/controller-managed-attach-detach:true
CreationTimestamp:Mon,2021年2月8日16:02:14+0530
污点:
计划外:错误
租赁:
持有人身份:ip-192-168-100-146.ec2.内部
获取时间:
更新时间:2021年2月8日星期一17:08:07+0530
条件:
键入状态LastHeartbeatTime LastTransitionTime原因消息
----             ------  -----------------                 ------------------                ------                       -------
MemoryPressure False Mon,2021年2月8日17:05:26+0530 Mon,2021年2月8日16:02:13+0530 KubeletHasSufficientMemory kubelet有足够的可用内存
磁盘压力假周一,2021年2月8日17:05:26+0530周一,2021年2月8日16:02:13+0530 KubelethasNode磁盘压力kubelet没有磁盘压力
PID压力假周一,2021年2月8日17:05:26+0530周一,2021年2月8日16:02:13+0530 Kubelethassufficient PID kubelet有足够的可用PID
Ready True Mon,08 Feb 2021 17:05:26+0530 Mon,08 Feb 2021 16:02:44+0530 KubeletReady kubelet正在发布就绪状态
地址:
内部IP:192.168.100.146
主机名:ip-192-168-100-146.ec2.internal
内部DNS:ip-192-168-100-146.ec2.internal
容量:
可附加卷aws ebs:39
中央处理器:1
短暂储存量:8376300Ki
hugepages-2Mi:0
内存:1006900Ki
豆荚:4
可分配:
可附加卷aws ebs:39
cpu:940m
短暂存储:6645856244
hugepages-2Mi:0
内存:598324Ki
豆荚:4
系统信息:
机器ID:4ec92546167f44ed87b3bccf78d597bb
系统UUID:EC247791-4550-81B2-5CE7-0B5ACD5E96C5
启动ID:15d14b07-6e8e-48ad-9e6f-71225d16ea3c
内核版本:4.14.209-160.339.amzn2.x86_64
操作系统映像:AmazonLinux2
操作系统:linux
架构:amd64
容器运行时版本:docker://19.3.6
Kubelet版本:v1.18.9-eks-d1db3c
Kube代理版本:v1.18.9-eks-d1db3c
ProviderID:aws:///us-east-1f/i-0b551804ff7079b95
非端接吊舱:(共4个)
命名空间名称CPU请求CPU限制内存请求内存限制使用年限
---------                   ----                       ------------  ----------  ---------------