Repository navigation
feat: store QdrantCluster snapshots in S3 - #333
Merged
Merged
Conversation
Add spec.config.storage.snapshots so the operator can store Qdrant snapshots in S3 instead of on each node's snapshot volume. The s3 member sets the bucket, region, endpoint URL and key prefix. It takes credentials only as Secret references or from a container credentials endpoint, never as values. Without credentials, Qdrant uses the pod's own cloud identity. The s3 member also takes timeout_sec, connect_timeout_sec, max_retries and retry_timeout_sec. Qdrant v1.20.0 added them to s3_config, and the operator renders them only for v1.20.0 or later. Both timeouts must be at least one second, as in Qdrant. CEL rules require exactly one backend and at most one kind of credentials. Envtest cases cover both rules, an empty bucket, the retry settings and a zero request timeout. Add NodeStatus.snapshotBackend and NodeStatus.snapshotMigration. The operator records in them whether a node keeps its snapshots on the snapshot volume or in object storage, and how far the copy between the two has progressed, including the copy back after the field is removed. Also add QdrantConfiguration.GetStorage, so callers can walk the storage settings without nil checks.
syndbg
force-pushed
the
feat/qdrantcluster-snapshot-object-storage
branch
from
November 3, 2026 13:47
6c462ac to
11c77f8
Compare
viktormetodiev
approved these changes
Nov 3, 2026
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.
Add spec.config.storage.snapshots so the operator can store Qdrant
snapshots in S3 instead of on each node's snapshot volume. The s3
member sets the bucket, region, endpoint URL and key prefix. It takes
credentials only as Secret references or from a container credentials
endpoint, never as values. Without credentials, Qdrant uses the pod's
own cloud identity.
The s3 member also takes timeout_sec, connect_timeout_sec, max_retries
and retry_timeout_sec. Qdrant v1.20.0 added them to s3_config, and the
operator renders them only for v1.20.0 or later. Both timeouts must be
at least one second, as in Qdrant.
CEL rules require exactly one backend and at most one kind of
credentials. Envtest cases cover both rules, an empty bucket, the retry
settings and a zero request timeout.
Add NodeStatus.snapshotBackend and NodeStatus.snapshotMigration. The
operator records in them whether a node keeps its snapshots on the
snapshot volume or in object storage, and how far the copy between the
two has progressed, including the copy back after the field is removed.
Also add QdrantConfiguration.GetStorage, so callers can walk the
storage settings without nil checks.