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

前端 未结 7 3881
一向
一向 2020-12-14 14:24

I try to set up Kubernetes cluster. I have Persistent Volume, Persistent Volume Claim and Storage class all set-up and running but when I wan to create pod from deployment,

7条回答
  •  温柔的废话
    2020-12-14 15:03

    The "1 node(s) had volume node affinity conflict" error is created by the scheduler because it can't schedule your pod to a node that conforms with the persistenvolume.spec.nodeAffinity field in your PersistentVolume (PV).

    In other words, you say in your PV that a pod using this PV must be scheduled to a node with a label of kubernetes.io/cvl-gtv-42.corp.globaltelemetrics.eu = master, but this isn't possible for some reason.

    There may be various reason that your pod can't be scheduled to such a node:

    • The pod has node affinities, pod affinities, etc. that conflict with the target node
    • The target node is tainted
    • The target node has reached its "max pods per node" limit
    • There exists no node with the given label

    The place to start looking for the cause is the definition of the node and the pod.

提交回复
热议问题