Skip to content
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

Add support for custom Persistent Volumes to enable GCS storage #381

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

seanson
Copy link

@seanson seanson commented Feb 24, 2025

In some environments, such as our Google Kubernetes Engine with Autopilot, there is no support for privileged containers to run the NFS provisioner or standard ReadWriteMany storage classes are too heavy. This PR adds the ability to declare a custom Persistent Volume configuration, which enables things like Google Cloud Storage via their FUSE CSI provider. This additional feature does not impact existing installations and I have included additional Helm unittest cases for it. I have tested this locally in our GKE cluster and it is working.

@seanson seanson requested a review from a team as a code owner February 24, 2025 08:58
Copy link

changeset-bot bot commented Feb 24, 2025

⚠️ No Changeset found

Latest commit: 053a054

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@seanson seanson force-pushed the feat_gcs_persistence branch from 55c3eb0 to 053a054 Compare February 24, 2025 09:13
@APErebus
Copy link
Contributor

Hi @seanson! Thanks for the PR.

Just letting you know our team is mostly unavailable this week so this might not get a review until next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants