Provide a stable client endpoint

Clients must not be pinned to only the current Active node. Configure both replica advertised URLs in the Gateway client—the supported HA model—or use a customer-managed VIP/load balancer as a convenience in front of them. A load balancer is not leadership election or fencing.

DNS names must resolve from each product installation and match the Gateway TLS certificate SAN when HTTPS is used. If using a VIP/load balancer, route lease mutations only to a target whose GET /readyz returns 200. /healthz means only that the HTTP process is alive and is insufficient for routing. Health probes are unauthenticated, but under mTLS transport the probe connection must still satisfy TLS client-certificate requirements.