The mounter can be set as a parameter in the storage class. You can also create multiple storage classes for each mounter if you like.
@@ -138,18 +137,6 @@ Characteristics of different mounters (for more detailed information consult the
* Files can be viewed normally with any S3 client
* Doesn't create directory objects like s3fs or GeeseFS
#### s3backer (experimental*)
* Represents a block device stored on S3
* Allows to use a real filesystem
* Files are not readable with other S3 clients
* Support appends
* Supports compression before upload (Not yet implemented in this driver)
* Supports encryption before upload (Not yet implemented in this driver)
*s3backer is experimental at this point because volume corruption can occur pretty quickly in case of an unexpected shutdown of a Kubernetes node or CSI pod.
The s3backer binary is not bundled with the normal docker image to keep that as small as possible. Use the `<version>-full` image tag for testing s3backer.