Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,13 @@ Such errors can also occur if the pods that should use the `volume` are located

If you need to use `ReadWriteMany`, we recommend using CSI for our object storage because the volumes based on it support this access mode:

Automatic installation via the marketplace or `Helm` chart is described [here](../../../docs/managed-kubernetes/operations/volumes/s3-csi-integration), and manual integration is described [here](../../../managed-kubernetes/operations/volumes/s3-csi-integration).
Automatic installation via the marketplace or `Helm` chart is described [here](../../../managed-kubernetes/operations/volumes/s3-csi-integration.md), and manual integration is described [here](../../../managed-kubernetes/operations/volumes/s3-csi-integration.md?tabs=instructions_manual).




## If the issue persists {#if-issue-still-persists}

If the actions described above did not help solve the issue, you can try to organize storage on your own. Some of the possible solutions also support multiple access (for example, nfs or CEPH). You can read more about this in the [k8s official documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes).