Name:           mongo-0
Namespace:      dynpv
Priority:       0
Node:           <none>
Labels:         app=mongo
                controller-revision-hash=mongo-6bdbdf9f6c
                statefulset.kubernetes.io/pod-name=mongo-0
Annotations:    <none>
Status:         Pending
IP:             
IPs:            <none>
Controlled By:  StatefulSet/mongo
Containers:
  mongo:
    Image:      mongo
    Port:       27017/TCP
    Host Port:  0/TCP
    Command:
      mongod
      --bind_ip_all
      --replSet
      rs0
    Environment:  <none>
    Mounts:
      /data/db from volume-mongo (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ptqcj (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  volume-mongo:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  volume-mongo-mongo-0
    ReadOnly:   false
  kube-api-access-ptqcj:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
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  4m7s  default-scheduler  running PreBind plugin "VolumeBinding": binding volumes: pv "pvc-a7a2fcaa-42ad-4fd9-a579-0b1ce5f31f45" node affinity doesn't match node "noeud1": no matching NodeSelectorTerms
  Warning  FailedScheduling  4m5s  default-scheduler  0/3 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/disk-pressure: }, 3 node(s) had volume node affinity conflict. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.