Pods consul and minio unable to run

Hi there, I am trying to install faas-flow-infra in my k8s master node.

After i run the code ./deploy_helm_chart.sh and check the pods with kubectl xxx.

I got following

[jairwu@kubemaster FaaSFlow]$ kubectl get pod -n faasflow
NAME                      READY   STATUS    RESTARTS   AGE
consul-0                  0/1     Pending   0          23m
jaeger-7557db4c5d-5c9hc   1/1     Running   0          23m
minio-77c964d7c5-ck2b4    0/1     Pending   0          23m

[jairwu@kubemaster FaaSFlow]$ kubectl describe pod consul-0 -n faasflow
Name:           consul-0
Namespace:      faasflow
Priority:       0
Node:           <none>
Labels:         app=consul
                component=server
                controller-revision-hash=consul-598b59f8d7
                statefulset.kubernetes.io/pod-name=consul-0
Annotations:    consul.hashicorp.com/connect-inject: false
Status:         Pending
IP:             
IPs:            <none>
Controlled By:  StatefulSet/consul
Containers:
  consul:
    Image:       consul:1.6.2
    Ports:       8500/TCP, 8400/TCP, 53/TCP, 8443/TCP, 8080/TCP, 8301/TCP, 8302/TCP, 8600/TCP, 8300/TCP
    Host Ports:  0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
    Args:
      agent
      -advertise=$(POD_IP)
      -bootstrap-expect=1
      -config-file=/etc/consul/config/server.json
    Environment:
      POD_IP:   (v1:status.podIP)
    Mounts:
      /consul/data from data (rw)
      /etc/consul/config from config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-kjt9c (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      consul-config
    Optional:  false
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  consul-pv-claim
    ReadOnly:   false
  kube-api-access-kjt9c:
    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  24m   default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling  24m   default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.

I am not sure it needs to create a PV or something, I am new to K8s. Could someone can give any suggestions?

[jairwu@kubemaster faas-flow-infra]$ kubectl get pv -n faasflow
No resources found

[jairwu@kubemaster FaaSFlow]$ kubectl get pvc -n faasflow
NAME              STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
consul-pv-claim   Pending                                                     26m
minio-pv-claim    Pending                                                     26m

[jairwu@kubemaster FaaSFlow]$ kubectl describe pvc consul-pv-claim -n faasflow
Name:          consul-pv-claim
Namespace:     faasflow
StorageClass:  
Status:        Pending
Volume:        
Labels:        app.kubernetes.io/managed-by=Helm
Annotations:   meta.helm.sh/release-name: faas-flow-infra
               meta.helm.sh/release-namespace: faasflow
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      
Access Modes:  
VolumeMode:    Filesystem
Used By:       consul-0
Events:
  Type    Reason         Age                   From                         Message
  ----    ------         ----                  ----                         -------
  Normal  FailedBinding  2m2s (x102 over 27m)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set

faasflow / faas-flow-infra

Pods consul and minio unable to run #6