Repository navigation
feat: add S3 TLS options and per-dataset NFS versions - #93
Merged
izturn merged 2 commits intoOct 16, 2026
Merged
Conversation
usernameisnull
force-pushed
the
feat/s3-https-nfs-per-version
branch
from
October 16, 2026 09:47
4529339 to
666dd62
Compare
Contributor
|
/lgtm |
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
2 participants
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.
S3 datasets now support configurable TLS verification, including system trust, custom CA certificates mounted from Kubernetes Secrets, and explicit verification bypass.
NFS datasets can override the controller's default protocol version through
source.options.nfsVersion. The override is validated and immutable after creation. Explicit URI ports are passed as mount options while preserving existing volume identities.