feat: allow RustFS to validate tenant storage layouts

[GatewayJ]

Type of Change

• New Feature
• Bug Fix
• Documentation
• Performance Improvement
• Test/CI
• Refactor
• Other:

Related Issues

Fixes #144

Summary of Changes

• Remove operator-side RustFS storage layout validation from the Tenant CRD and Console API paths.
• Keep only Kubernetes/operator constructability checks such as positive server and volume counts, unique pool names, peer DNS label length, and immutable existing pool shape.
• Render RUSTFS_VOLUMES as a local path only for a single-pool single-node single-disk Tenant; multi-pool tenants use peer DNS entries so RustFS receives an accurate global topology.
• Update Console defaults, examples, and user guides to show 1x1 development tenants and clarify that RustFS validates storage layout at startup.

Checklist

• I have read and followed the CONTRIBUTING.md guidelines
• Passed make pre-commit (fmt-check + clippy + test + console-lint + console-fmt-check)
• Added/updated necessary tests
• Documentation updated (if needed)
• CHANGELOG.md updated under [Unreleased] (N/A: this repository has no CHANGELOG.md)
• CI/CD passed (if applicable)

Impact

• Breaking change (CRD/API compatibility)
• Requires doc/config/deployment update
• Other impact: RustFS now owns storage layout, erasure set, and parity compatibility validation.

Verification

cargo test types::v1alpha1::tenant::workloads::tests::single_node_single_disk_statefulset_uses_local_rustfs_volume
cargo test types::v1alpha1::tenant::workloads::tests::mixed_pool_single_node_single_disk_uses_peer_dns_volume
make pre-commit
git diff --check

Additional Notes

This does not add a separate standalone mode. The operator only infers the local RUSTFS_VOLUMES=/data/rustfs0 form for the single-pool 1x1 case; other accepted layouts are passed through to RustFS with peer DNS topology.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dd48ba7c4a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid changing existing pool endpoint identity on expansion

When a Tenant starts as the new default single-pool 1x1 layout, this returns /data/rustfs0; after adding any second pool, the same existing pool no longer satisfies self.spec.pools.len() == 1, so its rendered RUSTFS_VOLUMES changes to the peer-DNS form. The reconciler treats env changes as StatefulSet updates, and pool lifecycle matching uses this same cmdline string, so expanding a 1x1 Tenant can restart the original pool with a different endpoint identity and then fail to match the pool RustFS already reports.

Useful? React with 👍 / 👎.