Name:             deployment-nfs-566fd889bc-v5ttk
Namespace:        default
Priority:         0
Service Account:  default
Node:             <none>
Labels:           name=deployment-nfs
                  pod-template-hash=566fd889bc
Annotations:      <none>
Status:           Pending
IP:               
IPs:              <none>
Controlled By:    ReplicaSet/deployment-nfs-566fd889bc
Containers:
  deployment-nfs:
    Image:      mcr.microsoft.com/oss/nginx/nginx:1.19.5
    Port:       <none>
    Host Port:  <none>
    Command:
      /bin/bash
      -c
      set -euo pipefail; while true; do echo $(hostname) $(date) >> /mnt/nfs/outfile; sleep 1; done
    Environment:  <none>
    Mounts:
      /mnt/nfs from nfs (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-lbqt7 (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  nfs:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  pvc-deployment-nfs
    ReadOnly:   false
  kube-api-access-lbqt7:
    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:              kubernetes.io/os=linux
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  4m46s (x2 over 10m)  default-scheduler  0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.