Hi Shannon,
I think this will be reworked as part of the FLIP-6 efforts. Your problem comes
up in Kubernetes where several JMs would sit behind a K8s service. I think the
solution is for the JMs to act as proxies (they contact the JM leader, get the
data and return to the client) instead of red
Is anyone running multiple JobManagers (in High Availability mode) behind a
load balancer such as an AWS ELB or a software proxy such as HAProxy or Nginx?
Right now, it appears that server-side redirects that come from the JobManager
Web UI use the internal IP address of the JobManager (from Akk
