Issue: DELETE /leader returns 503 on follower instead of forwarding stepdown request
Issue: DELETE /leader returns 503 on follower instead of forwarding stepdown request: a task in LegoFlow-SWE (Harbor dataset). Currently, when an HTTP DELETE request is sent to the /leader endpoint on a node that is not the leader, it returns a 503 Service Unavailable error. This is inconsistent…
The task
Currently, when an HTTP DELETE request is sent to the `/leader` endpoint on a node that is **not** the leader, it returns a `503 Service Unavailable` error. This is inconsistent with other cluster operations like `RemoveNode` and `Backup`, which automatically forward the request to the leader when the local call…
Part of Lego-X/LegoFlow-SWE.