26cb1d95e8
With this, each volume will get its own prefix within the bucket if it is configured in the storage class. This also ensures backwards compatibility with older volumes that have been created in earlier versions of csi-s3.
20 lines
815 B
YAML
20 lines
815 B
YAML
---
|
|
kind: StorageClass
|
|
apiVersion: storage.k8s.io/v1
|
|
metadata:
|
|
name: csi-s3
|
|
provisioner: ch.ctrox.csi.s3-driver
|
|
parameters:
|
|
# specify which mounter to use
|
|
# can be set to rclone, s3fs, goofys or s3backer
|
|
mounter: rclone
|
|
# to use an existing bucket, specify it here:
|
|
# bucket: some-existing-bucket
|
|
csi.storage.k8s.io/provisioner-secret-name: csi-s3-secret
|
|
csi.storage.k8s.io/provisioner-secret-namespace: kube-system
|
|
csi.storage.k8s.io/controller-publish-secret-name: csi-s3-secret
|
|
csi.storage.k8s.io/controller-publish-secret-namespace: kube-system
|
|
csi.storage.k8s.io/node-stage-secret-name: csi-s3-secret
|
|
csi.storage.k8s.io/node-stage-secret-namespace: kube-system
|
|
csi.storage.k8s.io/node-publish-secret-name: csi-s3-secret
|
|
csi.storage.k8s.io/node-publish-secret-namespace: kube-system
|