This message was deleted.

I think I understand your desire, that makes sense. Though this seems rather complicated and it'd fairly difficult to implement in a clean way.

Noted @dry-elephant-14928. Can i suggest the following to simplify the process and let us know your valuable revert feedback; • We introduce priority attribute for egress service config. • By default, if the priority is not set, it will assign "0" by default, which is highest priority ( to a server or cluster) and likewise one can set a priority number for the egress service cluster / docker / node. Eg : As of DNS - MX. records one can add multiple entries with priority and lowest will give highest priority while largest will have lowest priority. • When routing happens ( on egress requests) , apart from current routing logic we sort the egress available workers with priority ( as point 2 logic) and serve first available worker. We can keep egress node / cluster priority attribute in redis as well.