using the built-in balancer-manager ui or curl to disable a balancer member does not actually do anything. command: /usr/bin/curl --silent --insecure -o /dev/null -XPOST 'https://localhost:443/balancer-manager?' -d b=home.monolith.on1.saasure.net -d w=https://on1-lbmo01c.aue1t.internal -d nonce=20e16be2-eb5f-42c0-b061-57af2968c7db -d w_status_D=1 after running the above command, the status of the member reflects as changed, but traffic is still flowing to the host. LoadBalancer Status for balancer://home.monolith.on1.saasure.net [pb9c23464_home_monolith_on1_saasure_net] https://on1-lbmo01b.aue1t.internal 1.00 0 Init Ok 0 0 0 0 0 https://on1-lbmo01c.aue1t.internal 1.00 0 Init Dis 0 0 0 0 0
of note, there are no errors in the logs whenever the balancer-manager status is changed.