mirror of https://github.com/pgsty/minio.git synced 2026-08-09 07:43:29 +03:00

Files

T

Feng Ruohang c46b16ec62 chore: cut over to pgsty/silo and main

The transitional references land in one commit, because they are only correct
together: the repository is pgsty/silo, its default branch is main, and nothing
in the tree should point a user at the old names.

Changed:

- Workflow branch filters. go.yml and vulncheck.yml gated on `branches: master`
  for both push and pull_request, so renaming the default branch would have
  taken automatic CI offline with no error and no signal - the workflows would
  simply never trigger again. They now name main.
- Release target. goreleaser's `release.github.name` becomes silo, which is
  what actually decides where a tagged build publishes. sign-release-rpms.sh's
  GH_REPO default follows.
- The OCI `image.source` label, the Helm chart `sources` entry, the security
  advisory link in the issue-template config, and the go.mod comment citing the
  LDAP TLS fix.
- 115 occurrences across README, README_ZH, SECURITY, CONTRIBUTING and 30 docs
  pages, including 72 links that also carried the master branch in their path.
  Those matter most: GitHub redirects clone, fetch, push and web URLs after a
  rename, but raw.githubusercontent.com does not, and neither follows a branch
  rename - every one of those links would 404 twice over.
- Three error strings in cmd/erasure-sets.go, cmd/storage-errors.go and
  internal/config/errors.go that print an issue URL to operators. These are Go
  string literals inside rebrand-guard's brand allowlist, so the baseline is
  regenerated. The regeneration removes exactly those three entries and adds
  none; all twelve other protected sets, including the 9014 exported symbols,
  are byte-identical.
- The transitional-naming disclaimers in README, README_ZH, SECURITY and
  CONTRIBUTING are dropped, since they no longer describe anything.

Deliberately unchanged, all three because they exist to reject or freeze the old
name rather than to point at it:

- buildscripts/minio-upgrade.sh pins pgsty/minio@sha256:b6bfe72... - the frozen
  pre-rebrand image is the control group for the MinIO-to-Silo upgrade test.
- helm-migration-guard rejects any rendered container still pulling pgsty/minio.
- verify-rebrand.sh rejects the same in the delivery surfaces.

Also unchanged: docs/config/README.md links to pgsty/mc/blob/master, and that
repository's default branch really is still master. It moves when mc does.

verify-rebrand.sh gains three assertions so this cannot silently regress: no
source reference may name pgsty/minio outside the three allowlisted guards, no
link may target pgsty/silo's master branch, and go.yml and vulncheck.yml must
filter on main. Both new rejections were negative-tested - reintroducing a
master branch filter and adding a pgsty/minio URL each fail the gate with the
specific message.

This commit assumes the rename actually happens. Until the GitHub branch and
repository renames are executed, the links it introduces do not resolve.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-06 09:28:06 +08:00

5.8 KiB

Raw Blame History

Silo Server Limits Per Tenant

For optimal production setup Silo recommends Linux kernel version 4.x and later.

Erasure Code (Multiple Drives / Servers)

Item	Specification
Maximum number of servers per cluster	no-limit
Minimum number of servers	02
Minimum number of drives per server when server count is 1	02
Minimum number of drives per server when server count is 2 or 3	01
Minimum number of drives per server when server count is 4	01
Maximum number of drives per server	no-limit
Read quorum	N/2
Write quorum	N/2+1

Limits of S3 API

Item	Specification
Maximum number of buckets	unlimited (we recommend not beyond 500000 buckets) - see NOTE:
Maximum number of objects per bucket	no-limit
Maximum object size	50 TiB
Minimum object size	0 B
Maximum object size per PUT operation	5 TiB
Maximum number of parts per upload	10,000
Part size range	5 MiB to 5 TiB. Last part can be 0 B to 5 TiB
Maximum number of parts returned per list parts request	10000
Maximum number of objects returned per list objects request	1000
Maximum number of multipart uploads returned per list multipart uploads request	1000
Maximum length for bucket names	63
Maximum length for object names	1024
Maximum length for '/' separated object name segment	255
Maximum number of versions per object	10000 (can be configured to higher values but we do not recommend beyond 10000)

NOTE: While Silo does not implement an upper boundary on buckets, cluster hardware has natural limits that depend on workload and scaling patterns. Benchmark the intended workload and size production deployments with operational headroom.

List of Amazon S3 APIs not supported on Silo

We found the following APIs to be redundant or less useful outside of AWS S3. If you have a different view on any of the APIs we missed, please consider opening a GitHub issue with relevant details on why Silo must implement them.

List of Amazon S3 Bucket APIs not supported on Silo

BucketACL (Use bucket policies instead)
BucketCORS (CORS enabled by default on all buckets for all HTTP verbs, you can optionally restrict the CORS domains)
BucketWebsite (Use caddy or nginx)
BucketAnalytics, BucketMetrics, BucketLogging (Use bucket notification APIs)

List of Amazon S3 Object APIs not supported on Silo

ObjectACL (Use bucket policies instead)

Object name restrictions on Silo

Object name restrictions on Silo are governed by OS and filesystem limitations. For example object names that contain characters ^*|\/&"; are unsupported on Windows platform or any other file systems that do not support filenames with special characters.

This list is non exhaustive, it depends on the operating system and filesystem under use - please consult your operating system vendor for a more comprehensive list of special characters.

Silo recommends using Linux operating system for production workloads.

Objects must not have conflicting objects as parent objects, applications using this behavior should change their behavior and use non-conflicting unique keys, for example situations such as following conflicting key patterns are not supported.

PUT <bucketname>/a/b/1.txt
PUT <bucketname>/a/b

PUT <bucketname>/a/b
PUT <bucketname>/a/b/1.txt

5.8 KiB Raw Blame History