rascoe
It's also one of the reasons why so many people continue to use it. If you really need one of these services for your infrastructure, then your very likely going to be stuck using us-east-1. It may be quite some time before you get a 2nd region.
[1] https://aws.amazon.com/about-aws/global-infrastructure/regio...
While we aren't to the point of using cluster federation for production yet, this is the next logical step. I see a, not to distant, future where we have cluster federation across on premise, GCP, and AWS clusters.
If, like us, your all in on the container Kool-Aid, then I believe the future looks a lot like policy based Kubernetes scheduling across federated clusters. Policy factors like geolocation, spot pricing, resource requirements, SLOs, etc... are all configureable to the app developer and transparently effected by pluggable Kubernetes schedulers.