docs(transfer): document SQLite PVC deployment (#1040) - #83
Merged
Conversation
jlon
marked this pull request as ready for review
July 30, 2026 01:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document the chart-managed PVC used by the default single-replica SQLite Transfer store.
Issue Describe / Design
Related to CurvineIO/curvine#1040 and CurvineIO/curvine-helm#52.
An empty
transfer.storeUrlnow uses aReadWriteOncePVC selected by the cluster default StorageClass. The documentation distinguishes this durable single-replica mode from MySQL, which is required for multiple Transfer replicas and recommended for high availability.Changes
2-Deploy/.../01-k8s-Deployment.md2-Deploy/.../03-conf.mdTest verified
git diff --checknpm run buildDependencies