Rancher CAPI MachineDeployment node Ready status lag in UI

Rancher uses Cluster API to abstract infrastructure providers and manages node lifecycle through MachineDeployment objects. The Rancher UI reflects downstream cluster state via the cluster-agent and Rancher's internal resource cache.

An unresolved behavior concerns the timing of node Ready status updates in the Rancher UI versus the actual Kubernetes API state during rapid scaling events. The same cache layer can introduce a latency gap between a resource deletion in the downstream cluster and its removal from the Rancher dashboard. Behavior is expected to vary between Rancher versions, for example 2.6 versus 2.7+, due to changes in the CAPI integration layer, and registration path characteristics can affect synchronization perception.

The goal is to clarify the documented synchronization semantics for node status and cache refresh during CAPI-driven scaling.

What is the documented update path and expected latency for node Ready status from downstream Kubernetes to the Rancher UI? Under which Rancher and CAPI versions does the UI surface MachineDeployment status versus Node status? Is the observed cache latency for deletions a configurable behavior or a known limitation?