The Reaction Commerce[0] team is building their version of a modern eCommerce stack with Meteor[1]. They also received a Series A round of funding, lead by GV, in Oct '17 based on the work they've been doing[2]. [0]: https://reactioncommerce.com/ [1]: https://github.com/reactioncommerce/reaction [2]: https://venturebeat.com/2017/10/31/reaction-commerce-raises-...

We took the RBAC "hit" in 1.6. This mostly involved grokking the Role/RoleBinding and ClusterRole/ClusterRoleBinding details first. After that it was primarily a matter of updating a slew of Helm charts. Ones that we maintain for ourselves, and several community charts that had yet to be updated.

I think I understand cluster roles and bindings, my biggest thing is that I was using a bunch of off-the-shelf helm charts (for spinnaker, k8s dashboard, and deis workflow especially) and all three stopped working with RBAC. Those have been an...adventure to fix.

The AWS Global Infrastructure guide to all the Regions is pretty informative. When you look at the table here[1], you realize pretty quickly that every idea that AWS has ever had gets an initial deployment in Northern Virginia (us-east-1).

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...

I don't think switching will be the answer, but rather federation. We are currently deploying new services on Kubernetes and we can run isolated Kubernetes clusters on either GCP (not just GKE), or on AWS.

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.

Is it practical to replicate your data between clouds?

I would like to see the money go to Aaron's parents, Robert and Susan Swartz, in his memory. I believe they expended a tremendous amount financially in the legal fight for Aaron. It would seem fitting to extract some small measure of remuneration from MIT for their complicitness via this award.