Support for failover using latency routing

[gytis-ivaskevicius]

Is your feature request related to a problem?
We run applications in multiple regions and have latency routing set up, we wish to configure it so that if one region is unhealthy traffic would get routed to another region automatically

Describe the solution you'd like
I am not sure about implementation but I would expect to be able to easily implement this kind of routing.
If such routing was based on DNS, I'd expect some documentation on how to actually make it work.
If this feature was to be implemented on floating IPs then I would expect few extra annotations to configure it

Describe alternatives you've considered
None, currently we are trying to hack something together

[M00nF1sh]

such feature could only be implemented from ELB side.
Adding a ELB feature flag tag for our elb team.
/kind feature

[shraddhabang]

@gytis-ivaskevicius Have you looked into trying out using AWS Global accelerator with ALB for latency routing? We dont support this integration yet on our controller. But we can look into it if it solves your problem.

[gytis-ivaskevicius]

@shraddhabang This looks like exactly what we need! I'd love if you guys could add support for this

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten