gluster-csi-driver

该仓库包含Gluster的CSI（容器存储接口）驱动。容器存储接口（CSI）是一种行业标准，旨在实现集群级卷插件的标准化，使存储供应商（SP）只需开发一次插件，即可在多个容器编排（CO）系统中使用。

核心功能与特性

• 跨平台兼容性：遵循CSI标准，支持多种容器编排系统
• 多访问模式支持：提供RWO（单节点读写）和RWX（多节点读写）两种卷访问模式
• 动态卷供应：支持通过Kubernetes StorageClass动态创建存储卷
• 快照功能：支持卷快照创建、删除及从快照恢复新卷
• 灵活部署选项：可通过GCS工具一键部署，简化Kubernetes、GD2集群及CSI驱动的安装流程

构建GlusterFS CSI驱动

本仓库包含源代码和Dockerfile用于构建GlusterFS CSI驱动，采用多阶段容器构建方式，需使用较新版本的Docker或Buildah。

前置要求

• Docker或Buildah环境（推荐Docker 18.09+）
• 已安装Git工具

构建步骤

1. 克隆仓库并进入目录：

   bash
   [root@localhost]# git clone [***]
   [root@localhost]# cd gluster-csi-driver
   

2. 运行构建脚本：

   bash
   [root@localhost]# ./build.sh
   

使用方法与配置说明

前置部署

使用CSI驱动前需完成以下环境准备：

• 部署Kubernetes集群
• 部署GD2 Gluster集群

注意：可通过GCS工具一键部署上述环境，无需分别安装。详情参见GCS部署指南。

1. RWO卷声明（Gluster虚拟块CSI驱动）

部署CSI组件

bash
[root@localhost]# cd examples/kubernetes/gluster-virtblock/
[root@localhost]# kubectl create -f csi-deployment.yaml
service/csi-attacher-glustervirtblockplugin created
statefulset.apps/csi-attacher-glustervirtblockplugin created
daemonset.apps/csi-nodeplugin-glustervirtblockplugin created
service/csi-provisioner-glustervirtblockplugin created
statefulset.apps/csi-provisioner-glustervirtblockplugin created
serviceaccount/glustervirtblock-csi created
clusterrole.rbac.authorization.k8s.io/glustervirtblock-csi created
clusterrolebinding.rbac.authorization.k8s.io/glustervirtblock-csi-role created

创建存储类

yaml
# storage-class.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: glustervirtblock-csi
  annotations:
    storageclass.kubernetes.io/is-default-class: "false"
provisioner: org.gluster.glustervirtblock

bash
[root@localhost]# kubectl create -f storage-class.yaml
storageclass.storage.k8s.io/glustervirtblock-csi created

验证存储类创建：

bash
[root@localhost]# kubectl get storageclass
NAME                             PROVISIONER                    AGE
glustervirtblock-csi             org.gluster.glustervirtblock   6s

创建PersistentVolumeClaim (PVC)

yaml
# pvc.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: glusterblock-csi-pv
spec:
  storageClassName: glustervirtblock-csi
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 100Mi

bash
[root@localhost]# kubectl create -f pvc.yaml
persistentvolumeclaim/glusterblock-csi-pv created

验证PVC状态：

bash
[root@localhost]# kubectl get pvc
NAME                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS           AGE
glusterblock-csi-pv   Bound    pvc-1048edfb-1f06-11e9-8b7a-525400491c42   100Mi      RWO            glustervirtblock-csi   8s

创建使用PVC的Pod

yaml
# app.yaml
apiVersion: v1
kind: Pod
metadata:
  name: gluster-0
  labels:
    app: gluster
spec:
  containers:
  - name: gluster
    image: redis
    imagePullPolicy: IfNotPresent
    volumeMounts:
    - mountPath: "/mnt/gluster"
      name: glusterblockcsivol
  volumes:
  - name: glusterblockcsivol
    persistentVolumeClaim:
      claimName: glusterblock-csi-pv

bash
[root@localhost]# kubectl create -f app.yaml
pod/gluster-0 created

验证Pod状态及挂载：

bash
[root@localhost]# kubectl get pods
NAME        READY   STATUS    RESTARTS   AGE
gluster-0   1/1     Running   0          38s

[root@localhost]# kubectl exec -it gluster-0 -- mount | grep gluster
/mnt/blockhostvol/block_hosting_volume_ddd7ced7-7766-4797-9214-01fa9587472a/pvc-1048edfb-1f06-11e9-8b7a-525400491c42 on /mnt/gluster type xfs (rw,relatime,seclabel,attr2,inode64,noquota)

2. RWX卷声明（Gluster CSI驱动）

部署CSI组件

bash
[root@localhost]# kubectl create -f csi-deployment.yaml
service/csi-attacher-glusterfsplugin created
statefulset.apps/csi-attacher-glusterfsplugin created
daemonset.apps/csi-nodeplugin-glusterfsplugin created
service/csi-provisioner-glusterfsplugin created
statefulset.apps/csi-provisioner-glusterfsplugin created
serviceaccount/glusterfs-csi created
clusterrole.rbac.authorization.k8s.io/glusterfs-csi created
clusterrolebinding.rbac.authorization.k8s.io/glusterfs-csi-role created

注意：Kubernetes v1.13.1需启用特性门控：--feature-gates=VolumeSnapshotDataSource=true

创建存储类

yaml
# storage-class.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: glusterfs-csi
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: org.gluster.glusterfs

bash
[root@localhost]# kubectl create -f storage-class.yaml
storageclass.storage.k8s.io/glusterfs-csi created

创建PVC及Pod

步骤与RWO类似，PVC访问模式指定为ReadWriteMany，详细操作参见RWO卷声明部分。

快照功能使用

创建快照类

yaml
# snapshot-class.yaml
apiVersion: snapshot.storage.k8s.io/v1alpha1
kind: VolumeSnapshotClass
metadata:
  name: glusterfs-csi-snap
snapshotter: org.gluster.glusterfs

bash
[root@localhost]# kubectl create -f snapshot-class.yaml
volumesnapshotclass.snapshot.storage.k8s.io/glusterfs-csi-snap created

创建卷快照

yaml
# volume-snapshot.yaml
apiVersion: snapshot.storage.k8s.io/v1alpha1
kind: VolumeSnapshot
metadata:
  name: glusterfs-csi-ss
spec:
  snapshotClassName: glusterfs-csi-snap
  source:
    name: glusterfs-csi-pv
    kind: PersistentVolumeClaim

bash
[root@localhost]# kubectl create -f volume-snapshot.yaml
volumesnapshot.snapshot.storage.k8s.io/glusterfs-csi-ss created

从快照恢复卷

yaml
# pvc-restore.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: glusterfs-pv-restore
spec:
  storageClassName: glusterfs-csi
  dataSource:
    name: glusterfs-csi-ss
    kind: VolumeSnapshot
    apiGroup: snapshot.storage.k8s.io
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 5Gi

bash
[root@localhost]# kubectl create -f pvc-restore.yaml
persistentvolumeclaim/glusterfs-pv-restore created

高级配置

Thin Arbiter卷支持

创建支持Thin Arbiter的存储类：

yaml
# thin-arbiter-virtblock-storageclass.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: glustervirtblock-csi-thin-arbiter
provisioner: org.gluster.glustervirtblock
parameters:
  replicas: "2"
  arbiterType: "thin"
  arbiterPath: "192.168.122.121:/mnt/arbiter-path:24007"

loopback Bricks存储类

使用loopback设备作为brick的存储类：

yaml
# glusterfs-lite-storage-class.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: glusterfs-lite-csi
provisioner: org.gluster.glusterfs
parameters:
  brickType: "loop"