test: enhance e2e diagnostics for tenant readiness failures

[GatewayJ]

Type of Change

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

Related Issues

N/A

Summary of Changes

• Improve e2e live failure forensics by enriching Kubernetes snapshot collection.
• Add dedicated snapshot commands for tenant describe, PVC/PV/PV path visibility, RustFS pod logs (current + previous), and tenant/Pod descriptions.
• Add automatic snapshot diagnosis output (diagnosis.txt) and structured return values for easier failure handling.
• Detect and explain known startup signatures, including erasure read quorum and DNS lookup failures, with recovery guidance.
• In KindCluster cleanup/create flow, add explicit host storage directory checks:
  • pre-create reset requires directories to be empty,
  • post-delete requires directories to be absent.
• Keep diagnostic logic isolated in e2e harness/test layer only; no operator runtime behavior changes.

Checklist

• I have read and followed the CONTRIBUTING.md guidelines
• Passed make pre-commit
• Added/updated necessary tests
• Documentation updated (if needed)
• CHANGELOG.md updated under [Unreleased] (if user-visible change)
• CI/CD passed (if applicable)

Impact

• Breaking change (CRD/API compatibility)
• Requires doc/config/deployment update
• Other impact:
  • N/A

Verification

make pre-commit
cargo test --manifest-path e2e/Cargo.toml -- --quiet
cargo fmt --manifest-path e2e/Cargo.toml --check
cargo clippy --manifest-path e2e/Cargo.toml --all-targets -- -D warnings

Additional Notes

• This change intentionally keeps observability/debug instrumentation in e2e harness only.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5526485995

ℹ️ 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]

Clear TLS status when TLS is disabled

When spec.tls is removed or switched to Disabled, tls_plan.status is None and this branch skips any update to TLS fields, but StatusBuilder::from_tenant starts from the previous status snapshot. That leaves stale status.certificates.tls (and its old hash/error context) visible after TLS is turned off, which can mislead console/API consumers and automation that read tenant status. Please explicitly clear TLS status/condition when the plan is disabled.

Useful? React with 👍 / 👎.