Skip to content

feat: store QdrantCluster snapshots in S3 - #333

Merged
syndbg merged 1 commit into
mainfrom
feat/qdrantcluster-snapshot-object-storage
Nov 3, 2026
Merged

syndbg merged 1 commit into
mainfrom
feat/qdrantcluster-snapshot-object-storage

Conversation

@syndbg

@syndbg syndbg commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

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
syndbg requested a review from a team as a code owner October 31, 2026 15:09
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
syndbg force-pushed the feat/qdrantcluster-snapshot-object-storage branch from 6c462ac to 11c77f8 Compare November 3, 2026 13:47
@syndbg
syndbg merged commit 3fab7ec into main Nov 3, 2026
3 checks passed
@syndbg
syndbg deleted the feat/qdrantcluster-snapshot-object-storage branch November 3, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants