From 63b1f45dba317bc6d1a91522d75bacc859a373c6 Mon Sep 17 00:00:00 2001 From: Vitaliy Filippov Date: Wed, 21 Dec 2022 16:14:26 +0300 Subject: [PATCH] Add a note about static provisioning --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 89ff907..27bf62d 100644 --- a/README.md +++ b/README.md @@ -99,6 +99,12 @@ parameters: If the bucket is specified, it will still be created if it does not exist on the backend. Every volume will get its own prefix within the bucket which matches the volume ID. When deleting a volume, also just the prefix will be deleted. +### Static Provisioning + +If you want to mount a pre-existing bucket or prefix within a pre-existing bucket and don't want csi-s3 to delete it when PV is deleted, you can use static provisioning. + +To do that you should omit `storageClassName` in the `PersistentVolumeClaim` and manually create a `PersistentVolume` with a matching `claimRef`, like in the following example: [deploy/kubernetes/examples/pvc-manual.yaml](deploy/kubernetes/examples/pvc-manual.yaml). + ### Mounter We **strongly recommend** to use the default mounter which is [GeeseFS](https://github.com/yandex-cloud/geesefs).