[codex] add tenant status condition reconciliation#117
Merged
GatewayJ merged 2 commits intorustfs:mainfrom May 9, 2026
Merged
Conversation
1127bdb to
67bc255
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Change
Related Issues
N/A
Summary of Changes
Add a Tenant status condition framework for RustFS Operator and wire it into reconcile and Console APIs.
This PR introduces canonical condition types, reason values, condition upsert/sorting helpers, currentState summarization, and a runtime StatusBuilder. Reconcile now patches status before known early-return failures, records Events using the same stable reason as the condition, distinguishes direct pool deletion from pool rename, and avoids repeated no-op status patches.
Console list/detail/topology now read a shared status summary derived from status.conditions, including ready/reconciling/degraded flags, primary reason, stale generation detection, and next action hints.
Checklist
make pre-commit(fmt-check + clippy + test + console-lint + console-fmt-check)[Unreleased](if user-visible change)Impact
Verification
Additional Notes
next_actionsare generated from the status reason registry and are not written back to CR status.StatusPatchFailedwithout recursively patching status.Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.