Current implementation reproduces https://docs.google.com/document/d/1o6kd61gBVvUtYAqTN6JqJGlUAsatmlq2mmoBkQThEFg/edit for simplicity.

This has a caveat: when the management KAS SVC changes it would require changes to the .sh files setting binding the IP to the lo interface and the haproxies running in the dataplane.

We should find a way to either

• Ensure the IPs are always static for the kas SVCs so no need to worry about this.
• Or let them be static from the data plane pov, and the shared proxy would always use that same initial IP for discriminating but refresh the real IP that is forwarding requests to.
• Or find a way to refresh the IP on the flight dataplane side (seems unlikely since these are disk files, systemd services and static pods).
• Or use something else to use as the discriminating criteria.