Skip to content

docs: add Scality RING S3 CSI driver to production-grade drivers list #621

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

anurag4DSB
Copy link

This PR adds the Scality RING S3 CSI driver to the “Production Drivers” table in book/src/drivers.md.

Key details of the entry

  • Name: Scality RING S3 CSI
  • CSI driver name: s3.csi.scality.com
  • Compatible CSI versions: v1.11.0
  • Description: Container Storage Interface (CSI) driver that enables Kubernetes workloads to mount Scality RING S3 buckets as POSIX-like file-system volumes via Mountpoint-for-S3.
  • Persistence: Persistent
  • Supported access modes: Read/Write Multiple Pods (ReadWriteMany)
  • Dynamic provisioning: Not yet (static provisioning only)
  • Other features: — (left blank)

Documentation: https://scality.github.io/mountpoint-s3-csi-driver/

Added entry for `s3.csi.scality.com` driver that enables mounting
Scality RING S3 buckets as file system volumes in Kubernetes.

Documentation: https://scality.github.io/mountpoint-s3-csi-driver/
…y-CSI-driver-to-official-kubernetes-documentation

Add Scality RING S3 CSI driver to production drivers list
@k8s-ci-robot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Jun 25, 2025
Copy link

linux-foundation-easycla bot commented Jun 25, 2025

CLA Not Signed

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anurag4DSB
Once this PR has been reviewed and has the lgtm label, please assign xing-yang for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jun 25, 2025
@k8s-ci-robot
Copy link
Contributor

Welcome @anurag4DSB!

It looks like this is your first PR to kubernetes-csi/docs 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/docs has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 25, 2025
@xing-yang
Copy link
Contributor

Please fix the CLA issue.

@anurag4DSB
Copy link
Author

Please fix the CLA issue.

We are working on this. Thank you for the guidance.
I will update the PR once our organization has approved me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants