cds-csi-driver

A Container Storage Interface (CSI) Driver for Capitalonline(aka. CDS) cloud. This CSI plugin allows you to use CDS storage with the kubernetes cluster hosted or managed by CDS.

It currently supports CDS File Storage(NAS) and CDS Object Storage Service(OSS). The support for the Block Storage will be added soon.

To deploy

To deploy the CSI NAS driver to your k8s, simply run:

kubectl create -f https://raw.githubusercontent.com/capitalonline/cds-csi-driver/master/deploy/nas/deploy.yaml

To deploy the CSI OSS driver to your k8s, simply run:

# need install s3fs in host
# ubuntu OS
apt install s3fs -y

# centos OS
yum install s3fs -y

# install csi 
kubectl create -f https://raw.githubusercontent.com/capitalonline/cds-csi-driver/master/deploy/oss/deploy.yaml

To deploy the CSI EBS-DISK driver to your k8s, simply run:

deploy and update the driver settings

kubectl create -f https://raw.githubusercontent.com/capitalonline/cds-csi-driver/master/deploy/ebs_disk/base.yaml

set base64 access_key_id/access_key_secret into secret cck-secrets

apiVersion: v1
kind: Secret
metadata:
  name: cck-secrets
  namespace: kube-system
type: Opaque
data:
  access_key_id: ''
  access_key_secret: ''

PS: generate base64 ak/sk

import base64

# write here
ak = ''
sk = ''
access_key_id = str(base64.b64encode(str.encode(ak)), encoding="utf-8")
print('access_key_id:\n', access_key_id)
access_key_secret = str(base64.b64encode(str.encode(sk)), encoding="utf-8")
print('access_key_secret:\n', access_key_secret)

deploy driver service

kubectl create -f https://raw.githubusercontent.com/capitalonline/cds-csi-driver/master/deploy/ebs_disk/deploy.yaml

To deploy the CSI CCS-DISK driver to your k8s, simply run:

deploy and update the driver settings

kubectl create -f https://raw.githubusercontent.com/capitalonline/cds-csi-driver/master/deploy/ccs_disk/base.yaml

set base64 access_key_id/access_key_secret into secret ccs-secrets

apiVersion: v1
kind: Secret
metadata:
  name: ccs-secrets
  namespace: kube-system
type: Opaque
data:
  access_key_id: ''
  access_key_secret: ''

PS: generate base64 ak/sk

import base64

# write here
ak = ''
sk = ''
access_key_id = str(base64.b64encode(str.encode(ak)), encoding="utf-8")
print('access_key_id:\n', access_key_id)
access_key_secret = str(base64.b64encode(str.encode(sk)), encoding="utf-8")
print('access_key_secret:\n', access_key_secret)

deploy driver service

kubectl create -f https://raw.githubusercontent.com/capitalonline/cds-csi-driver/master/deploy/ccs_disk/deploy.yaml

To run tests

NAS:

Make sure that you have a Kubernetes cluster accessible with kubectl
Provision a nfs server with exports /nfsshare *(insecure,rw,async,no_root_squash,fsid=1000)
Run make test-prerequisite to build the image and deploy the driver to your k8s cluster
Run sudo NFS=<your nfs server ip> make test

OSS:

Make sure that you have a Kubernetes cluster accessible with kubectl
Register a Storage Service in CDS
Run make test-prerequisite to build the image and deploy the driver to your k8s cluster
Run make oss-test

To use the NAS driver

Examples can be found here

Static PV

pv.yaml

spec:
  csi:
    driver: nas.csi.cds.net
    volumeHandle: <name of the pv>
    volumeAttributes:
      server: "140.210.75.196"
      path: "/nfsshare/nas-csi-cds-pv"

Description:

Key	Value	Required	Description
driver	nas.csi.cds.net	yes	CDS csi driver's name
volumeHandle	<pv_name>	yes	Should be same with pv name
server	e.g. 140.210.75.195	yes	the mount point of the nfs server,can be found on NAS product list
path	e.g. /nfsshare/division1	yes	the path that the pv will use on the nfs server. It must start with `/nfsshare`. Each pv will use a separate directory(e.g `/nfsshare/division1/volumeHandleValue"`when `allowShared` is `false`. Otherwsise, the path of pv will be the same to `path`, which means all PVs with the same path will share data
vers	`3` or `4.0`	no	the protocol version to use for the nfs mount. if not provided, `4.0` will be used by default
options	e.g. `noresvport`	no	options for the nfs mount. If not provided it will be set to `noresvport` for `vers=4.0` and `noresvport,nolock,tcp` for `vers=3`
mode	e.g. `0777`	no	to customize the mode of the path created on nfs server. If not provided, the server's default mask will be used
modeType	e.g `recursive` or `non-recursive`	no	This tells the driver if the chmod should be done recursively or not. Only works when `mode` is specified. Default to `non-recursive`
allowShared	`"true"` or `"false"`	no	default to `"false`. If set, the data of all PVs with the same path will be shared

Dynamic PV

volumeAs: subpath

sc.yaml

provisioner: nas.csi.cds.net
reclaimPolicy: Delete
parameters:
  volumeAs: subpath
  servers: 140.210.75.194/nfsshare/nas-csi-cds-pv, 140.210.75.195/nfsshare/nas-csi-cds-pv
  server: 140.210.75.195
  path: /nfsshare
  vers: 4.0
  strategy: RoundRobin
  options: noresvport
  archiveOnDelete: true

Description:

Key	Value	Required	Description
provisioner	nas.csi.cds.net	yes	CDS csi driver's name
reclaimPolicy	Delete \| Retain	yes	`Delete` means that PV will be deleted with PVC delete `Retain` means that PV will be retained when PVC delete
volumeAs	subpath	no	Default is `subpath` `subpath` means each PV will be provisioned on a specified NAS server. `filesystem` means each PV will be provision with a new NAS Storage and use the storage exclusively.
servers	eg. 140.210.75.194/nfsshare/nas-csi-cds-pv, 140.210.75.195/nfsshare/nas-csi-cds-pv	no	multi servers are supported by a StorageClass. It should be separated by "," between each server/path.
server	e.g. 140.210.75.195	no	the mount point of the nfs server,can be found on NAS product list
strategy	e.g. RoundRobin	no	Only used for multi servers option. The value is supposed to be "RoundRobin" or "Random". The default value is "RoundRobin"
path	e.g. /nfsshare	no	the root path that the pv will dynamically provisioned on the NAS server. It must start with `/nfsshare`.
vers	`3` or `4.0`	no	the protocol version to use for the nfs mount. if not provided, `4.0` will be used by default
options	e.g. `noresvport`	no	options for the nfs mount. If not provided it will be set to `noresvport` for `vers=4.0` and `noresvport,nolock,tcp` for `vers=3`
mode	e.g. `0777`	no	to customize the mode of the path created on nfs server. If not provided, the server's default mask will be used
modeType	e.g `recursive` or `non-recursive`	no	This tells the driver if the chmod should be done recursively or not. Only works when `mode` is specified. Default to `non-recursive`
archiveOnDelete	`"true"` or `"false"`	no	only works when the `reclaim police` is `delete`. if `true`, the content of the pv will be archived on nfs instead of be deleted. Default to `false`

Kindly Remind:

a) server and path are as a whole to use.

b) servers and server cant be empty together. It means that servers or server is not empty at least in one yaml.

volumeAs: filesystem

sc.yaml

provisioner: nas.csi.cds.net
reclaimPolicy: Delete
parameters:
  volumeAs: filesystem
  protocolType: NFS
  storageType: high_disk
  siteID: *** 
  clusterID: *** 
  deleteVolume: true

Description:

Key	Value	Required	Description
provisioner	nas.csi.cds.net	yes	CDS csi driver's name
reclaimPolicy	Delete \| Retain	yes	`Delete` means that PV will be deleted with PVC delete `Retain` means that PV will be retained when PVC delete
volumeAs	filesystem	yes	Default is `subpath` `subpath` means each pv will be provisioned on a specified NAS server. `filesystem` means each PV will be provision with a new NAS Storage and use the storage exclusively.
storageType	high_disk	yes	Must be 'high_disk', only support 'high_disk'
siteID	***	yes	Cluster's site_id
clusterID	***	yes	cluster_id
deleteVolume	true \| false	no	Optional, default is 'false' `false` means that NAS storage will retain when PV delete `true` means that NAS storage will be deleted with PV delete
protocolType	NFS	no	Optional, default is 'NFS' must be 'NFS', only support 'NFS'

To use the OSS driver

Examples can be found here

Static PV

pv.yaml

spec:
  csi:
    driver: oss.csi.cds.net
    # set volumeHandle same value pv name
    volumeHandle: <name of the pv>
    volumeAttributes:
      bucket: "***"
      url: "http://oss-cnbj01.cdsgss.com"
      akId: "***"
      akSecret: "***"
      path: "***"

Description:

Key	Value	Required	Description
driver	oss.csi.cds.net	yes	CDS csi driver's name
volumeHandle		yes	Should be same with pv name
bucket		yes	Register in CDS and get one unique name
url	`http://oss-cnbj01.cdsgss.com`	yes	Should be `http://oss-cnbj01.cdsgss.com`
akId	<access_key>	yes	Get it from your own bucket's in CDS web
akSecret	<acckedd_key_secret>	yes	Get it from your own bucket's in CDS web
path	<bucket_path>	yes	Bucket path, default is `/`

To use the EBS-DISK driver

Examples can be found here

Dynamic Pv

sc.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: ebs-disk-csi-cds-sc
parameters:
  fsType: ext4
  region: SR_SaoPaulo
  zone: SR_SaoPaulo_A
  storageType: SSD
provisioner: ebs-disk.csi.cds.net
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true
allowedTopologies:
- matchLabelExpressions:
  - key: topology.kubernetes.io/region
    values:
    - SR_SaoPaulo
  - key: topology.kubernetes.io/zone
    values:
    - SR_SaoPaulo_A

Description:

Key	Value	Required	Description
fsType	[ xfs\|ext4 ]	yes	Linux filesystem type
storageType	[ ssd_disk ]	yes	Only support `ssd_disk`.
zong	Eg. "SR_SaoPaulo_A"	yes	Cluster's az code.
region	Eg. "SR_SaoPaulo"	yes	Cluster's region code
provisioner	ebs-disk.csi.cds.net	yes	Disk driver which installed default.
reclaimPolicy	[ Delete\|Retain ]	yes	`Delete` means that PV will be deleted with PVC delete `Retain` means that PV will be retained when PVC delete
volumeBindingMode	WaitForFirstConsumer	yes	Only suport `WaitForFirstConsumer` pollicy for disk.csi.cds.net driver.
allowedTopologies	matchLabelExpressions	no	Only suport `topology.kubernetes.io/zone`, `topology.kubernetes.io/region` pollicy for disk.csi.cds.net driver.

Kindly Remind:

For disk storage, recommending using volumeBindingMode: WaitForFirstConsumer in SC.yaml.

If not, please apply your ebs-disk.csi.cds.net csi driver's csi-provisioner in k8s with following:

Disk expansion:

kubectl patch pvc disk-csi-cds-pvc -p '{"spec":{"resources":{"requests":{"storage":"32Gi"}}}}'

To use the EKS-DISK driver

Examples can be found here

Dynamic Pv

sc.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: test-sc-retain
parameters:
  fsType: ext4
  storageType: SSD
  region: CN_Suqian
  zone: CN_Suqian_B
provisioner: eks-disk.csi.cds.net
reclaimPolicy: Retain
volumeBindingMode: WaitForFirstConsumer

Description:

Key	Value	Required	Description
fsType	[ xfs\|ext4 ]	yes	Linux filesystem type
storageType	[ SSD ]	yes	Only support `ssd_disk`
zone	Eg. " CN_Suqian_B"	yes	Cluster's az code.
region	Eg. " CN_Suqian"	yes	Cluster's region code.
provisioner	eks-disk.csi.cds.net	yes	Disk driver which installed default.
reclaimPolicy	[ Delete\|Retain ]	yes	`Delete` means that PV will be deleted with PVC delete `Retain` means that PV will be retained when PVC delete
volumeBindingMode	WaitForFirstConsumer	yes	Only suport `WaitForFirstConsumer` pollicy for disk.csi.cds.net driver.

Kindly Remind:

For disk storage, recommending using volumeBindingMode: WaitForFirstConsumer in SC.yaml.

If not, please apply your eks-disk.csi.cds.net csi driver's csi-provisioner in k8s with following:

To use the Disk driver

Dynamic PV

sc.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: disk-csi-cds-sc
parameters:
  fsType: "ext4"			
  storageType: "high_disk"
  iops: "3000"
  siteId: "beijing001"
  zoneId: "WuxiA-POD10-CLU02"
provisioner: disk.csi.cds.net
reclaimPolicy: Retain
volumeBindingMode: WaitForFirstConsumer

Description:

Key	Value	Required	Description
fsType	[ xfs\|ext4\|ext3 ]	yes	Linux filesystem type
storageType	[ high_disk\|ssd_disk ]	yes	Only support `high_disk` and `ssd_disk`. `high_disk` shoud be with iops `3000`. `ssd_disk` should be with iops `[5000
iops	[3000\|5000\|7500\|10000]	yes	Only support `3000` `5000` `7500` and `1000`. Should combined with `storageType`.
siteId	Eg. "Beijing001"	yes	Cluster's site_id.
zoneId	Eg. "Beijing-POD10-CLU02"	yes	Cluster's id.
provisioner	disk.csi.cds.net	yes	Disk driver which installed default.
reclaimPolicy	[ Delete\|Retain ]	yes	`Delete` means that PV will be deleted with PVC delete `Retain` means that PV will be retained when PVC delete
volumeBindingMode	WaitForFirstConsumer	yes	Only suport `WaitForFirstConsumer` pollicy for disk.csi.cds.net driver.

Kindly Remind:

For disk storage, recommending using volumeBindingMode: WaitForFirstConsumer in SC.yaml.

If not, please apply your disk.csi.cds.net csi driver's csi-provisioner in k8s with following:

- args: 
    - "--csi-address=$(ADDRESS)"
    - "--v=5"
    - "--feature-gates=Topology=true"			# 添加这个参数，开启 Topology 
  env: 
    - 
      name: ADDRESS
      value: /socketDir/csi.sock
  image: "registry-bj.capitalonline.net/cck/csi-provisioner:v1.5.0"
  name: csi-provisioner
  volumeMounts: 
    - 
      mountPath: /socketDir
      name: socket-dir

and then refer the following SC.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: disk
parameters:
  fstype: "ext4" 
  storageType: "high_disk"
  iops: "3000"
  siteId: "ca0bd848-9b59-40a2-9f57-d64fbc72a9df"
provisioner: disk.csi.cds.net
reclaimPolicy: Delete
volumeBindingMode: Immediate    # Immediate policy in SC 
allowedTopologies:				# using allowedTopologies in sc 
- matchLabelExpressions:
  - key: topology.kubernetes.io/zone	
    values:
    - WuxiA-POD10-CLU02

To use the CCS-DISK driver

Examples can be found here

Dynamic Pv

sc.yaml

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: ccs-disk-csi-cds-sc
parameters:
  fsType: ext4
  iops: "3000"
  siteId: "xxx"
  zoneId: Cluster_Name1
  storageType: "ssd_disk"
provisioner: ccs-disk.csi.cds.net
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
allowVolumeExpansion: true

Description:

Key	Value	Required	Description
fsType	[ xfs\|ext4\|ext3 ]	yes	Linux filesystem type
storageType	[ ssd_disk ]	yes	Only support `ssd_disk`
iops	[5000\|7500\|10000]	yes	Only support `5000` `7500` and `10000`. Should combined with `storageType`.
siteId	Eg. "Beijing001"	yes	Cluster's site_id.
zoneId	Eg. "Beijing-POD10-CLU02"	yes	Cluster's id.
provisioner	ccs-disk.csi.cds.net	yes	Disk driver which installed default.
reclaimPolicy	[ Delete\|Retain ]	yes	`Delete` means that PV will be deleted with PVC delete `Retain` means that PV will be retained when PVC delete
volumeBindingMode	WaitForFirstConsumer	yes	Only suport `WaitForFirstConsumer` pollicy for disk.csi.cds.net driver.

Kindly Remind:

For disk storage, recommending using volumeBindingMode: WaitForFirstConsumer in SC.yaml.

If not, please apply your ccs-disk.csi.cds.net csi driver's csi-provisioner in k8s with following:

Name		Name	Last commit message	Last commit date
Latest commit History 401 Commits
cmd		cmd
deploy		deploy
dist		dist
example		example
pkg		pkg
test		test
.gitignore		.gitignore
Dockerfile		Dockerfile
Dockerfile-old		Dockerfile-old
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
go.mod		go.mod
go.sum		go.sum
test.sh		test.sh

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

cds-csi-driver

To deploy

To run tests

To use the NAS driver

Static PV

Dynamic PV

volumeAs: subpath

volumeAs: filesystem

To use the OSS driver

Static PV

To use the EBS-DISK driver

Dynamic Pv

To use the EKS-DISK driver

Dynamic Pv

To use the Disk driver

Dynamic PV

To use the CCS-DISK driver

Dynamic Pv

About

Releases 27

Packages

Contributors 12

Languages

License

capitalonline/cds-csi-driver

Folders and files

Latest commit

History

Repository files navigation

cds-csi-driver

To deploy

To run tests

To use the NAS driver

Static PV

Dynamic PV

volumeAs: subpath

volumeAs: filesystem

To use the OSS driver

Static PV

To use the EBS-DISK driver

Dynamic Pv

To use the EKS-DISK driver

Dynamic Pv

To use the Disk driver

Dynamic PV

To use the CCS-DISK driver

Dynamic Pv

About

Resources

License

Stars

Watchers

Forks

Releases 27

Packages 0

Contributors 12

Languages

Packages