Why This Matters
Some operational actions, such as hibernation and primary-update approval, are controlled through annotations. Annotations work, but they are hard to discover, easy to mistype, and less ergonomic for GitOps systems, dashboards, and platform APIs than typed fields or action resources.
For production operators, these workflows should be obvious, auditable, and easy to automate.
Implementation Scope
- Evaluate moving operational actions from annotations into typed API fields or dedicated action resources.
- Cover at least hibernation and primary-update approval.
- Preserve backward compatibility for existing annotation-based workflows during a transition period.
- Add status conditions that clearly report pending, approved, running, and completed operation states.
- Document examples for kubectl, GitOps, and controller-driven automation.
- Add tests for both typed and legacy annotation paths if both remain supported.
Expected Capability
After this is implemented, users should be able to perform common RedisCluster operations through a discoverable typed API. Platform and GitOps integrations should be able to model these actions without relying on undocumented or stringly typed annotations.
Why This Matters
Some operational actions, such as hibernation and primary-update approval, are controlled through annotations. Annotations work, but they are hard to discover, easy to mistype, and less ergonomic for GitOps systems, dashboards, and platform APIs than typed fields or action resources.
For production operators, these workflows should be obvious, auditable, and easy to automate.
Implementation Scope
Expected Capability
After this is implemented, users should be able to perform common RedisCluster operations through a discoverable typed API. Platform and GitOps integrations should be able to model these actions without relying on undocumented or stringly typed annotations.