Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
neonvm-controller: Don't retry update on conflict (#796)
The previous logic would: 1. Try to update the status 2. If we got a conflict, overwrite the current VirtualMachine object equal to the state on the API server 3. Then, retry with the udpated object (without changing anything!) This is basically doing extra work for nothing! We discussed potentially changing this to overwrite the status on conflict, but this could result in issues when operating on stale data (e.g., overwriting .status.podName back to "" after it was already created). ref https://www.notion.so/neondatabase/Autoscaling-Team-Internal-Sync-179c7d597dbb4fe5b565d9c482d4d166 ref https://neondb.slack.com/archives/C03TN5G758R/p1707414998235459
- Loading branch information