abelinkinbio
commented
2 years ago @michaelwu0505 thanks for submitting this feature request. Would you mind sharing a little bit more about what you're aiming to accomplish with this architecture? Also, what does your current deployment look like today?
Generally, we recommend deploying cloudflared as "close" to your origin server as possible to reduce latency. However, in this example, it sounds like you may be leveraging either replicas or multiple tunnels. Have you considered utilizing our load balancing solution to intelligently steer traffic towards your origin servers in distinct geographies?
Describe the feature you'd like Cloudflare tunnel equivalent of multi-casting.
When there are multiple origin servers located at geographically far apart locations, each connected to a near by Cloudflare Edge, I would like the incoming request to be directed to the nearest Cloudflare Edge.
For example, if there are two origin servers. One is at the US, which is connected to LAX. Another is at Singapore and is connected to SIN. When there is a client coming from Japan, I would expect the request is forwarded to the Singapore origin through SIN PoP.
Describe alternatives you've considered Alternative is to not use Cloudflare tunnel and use origin IP that supports multi-casting.