-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
The operator needs comprehensive status condition management to provide clear visibility into the reconciliation state of Tenant resources. This includes standard Kubernetes conditions like Ready, Progressing, and Degraded.
Current Behavior
- Basic status updates exist but lack comprehensive condition management
- TODO comment at
src/reconcile.rs:92: "Implement comprehensive status condition updates on errors (Ready, Progressing, Degraded)" - Limited visibility into reconciliation progress and errors
Desired Behavior
Implement standard Kubernetes status conditions:
- Ready: Tenant is fully reconciled and operational
- Progressing: Tenant is being reconciled (creating/updating resources)
- Degraded: Tenant has errors or issues that need attention
Each condition should include:
- Status (True/False/Unknown)
- Reason (machine-readable identifier)
- Message (human-readable description)
- LastTransitionTime
Implementation Considerations
- Add
Conditionsfield to TenantStatus - Update conditions throughout reconciliation loop
- Set appropriate conditions on errors via
error_policy() - Add helper functions for condition management
- Update examples and documentation
Priority
High - Core Stability (from ROADMAP.md)
Related
- Referenced in:
src/reconcile.rs:92 - Status types in:
src/types/v1alpha1/status/ - Part of: Core Stability roadmap phase
Metadata
Metadata
Assignees
Labels
No labels