mirror of https://github.com/rustfs/rustfs.git synced 2026-09-10 14:16:01 +00:00

Files

T

houseme 8b66e9b62a test(scanner): plan Linux evidence validation (#7620 )

Add a Scanner/Heal Linux release-evidence planner that emits a machine-readable execution manifest for the remaining measured validation lanes.

The planner can run only lightweight preflight checks and keeps plan-only output distinct from measured release evidence.

Co-authored-by: zhi22915 <qiuzgang@gmail.com>

2026-09-10 14:09:13 +08:00

architecture

feat(ilm): backfill proven legacy transition state (#7591 )

2026-09-09 23:40:30 +08:00

operations

feat(ilm): inspect legacy transition version state (#7581 )

2026-09-09 19:01:01 +08:00

postmortems

fix(replication): send an integrity header on Object Lock PUTs (#7097 )

2026-09-03 20:26:44 +08:00

testing

test(scanner): plan Linux evidence validation (#7620 )

2026-09-10 14:09:13 +08:00

README.md

fix(metrics): prevent duplicate drive reporting across nodes (#7582 )

2026-09-09 19:00:20 +08:00

README.md

Documentation

Use the focused indexes rather than treating this directory as an unordered collection:

Operations

Operational runbooks live under operations/. Replication operators should start with:

Runbook	Use it for
Site replication operations	Health fields, pending operations, outage recovery, re-pair admission, IAM/SSE boundaries, and upgrades.
Replication target check	Validating an S3 destination and version fidelity before enabling replication.
Replication object size limits	Multipart routing, large-object limits, and retry characteristics.
Replication outbound transport	Integrity headers, generic target behavior, and transport knobs.

Other runbooks remain grouped by filename in operations/; architecture pages link to the relevant runbook where a cross-boundary procedure is required.

For storage dashboards, see Storage metrics and observer selection: drive ownership, snapshot freshness, counter queries, and rolling upgrades.