The test intermittently gets 503 responses immediately after the
configuration becomes valid. Possibly because the controller is
still updating the config, or the probe settings do not set the
backend as healthy on startup.

This is a workaround until the cause is clarified.