​PVC 通过 NFS Provisioner 自动创建 PV 的流程及鉴权，超详细~~~

关于鉴权的问题。铁铁可能遇到了RBAC配置的问题，所以现在明确整个过程中各个组件需要的权限，ServiceAccount、ClusterRole、ClusterRoleBinding的作用，鉴权的大致步骤。

接下来我将分步骤详细说明自动创建PV的过程，创建PVC，到Kubernetes发现StorageClass，触发Provisioner，Provisioner创建PV，最后绑定PVC和PV，以及核心组件的作用。

1.大致流程

 nfs-provisioner-deploy.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nfs-provisioner
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nfs-provisioner
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: nfs-provisioner
    spec:
      serviceAccountName: nfs-provisioner
      containers:
      - name: nfs-provisioner
        image: registry.cn-beijing.aliyuncs.com/pylixm/nfs-subdir-external-provisioner:v4.0.0
        volumeMounts:
        - name: nfs-root
          mountPath: /persistentvolumes
        env:
        - name: PROVISIONER_NAME
          value: my/nfs-provisioner  # Provisioner 标识符
        - name: NFS_SERVER
          value: 192.168.111.100
        - name: NFS_PATH
          value: /shared     # NFS 共享目录
      volumes:
      - name: nfs-root
        nfs:
          server: 192.168.111.100
          path: /shared

 nfs-provisioner-SA.yaml

apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-provisioner
  namespace: default