You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/en/adminGuide/use-woodpecker.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,6 +96,28 @@ Notes:
96
96
- With `minio`, Woodpecker shares the same object storage with Milvus (MinIO/S3/GCS/OSS, etc.).
97
97
- With `local`, a single‑node local disk is only suitable for Standalone. If all pods can access a shared file system (e.g., NFS), Cluster mode can also use `local`.
98
98
99
+
## Object storage compatibility for `storage.type=minio`
100
+
101
+
The following matrix summarizes the currently known compatibility of object storage backends when Woodpecker is configured with `storage.type=minio`. This information is based on [GitHub Discussion #150](https://github.com/zilliztech/woodpecker/discussions/150).
| VAST Data | Supported | Verified by the community; works with non-versioned buckets only. |
113
+
| Other S3-compatible storage | Partial | Depends on full support for S3 Conditional Write semantics. |
114
+
115
+
Notes:
116
+
117
+
- Compatibility depends on native SDK support or support for S3 Conditional Write semantics.
118
+
- If you self-host MinIO for Woodpecker, use `RELEASE.2024-12-18T13-15-44Z` or later.
119
+
- This matrix reflects [the current discussion](https://github.com/zilliztech/woodpecker/discussions/150) and may evolve as backend support is validated further.
120
+
99
121
## Deployment guides
100
122
101
123
### Enable Woodpecker for a Milvus Cluster on Kubernetes (Milvus Operator, storage=minio)
0 commit comments