Re:Docker in Production: A History of Failure
by boulos on Saturday November 05, 2016 @04:36PM
(#12881751)
Thanks for the reply; we'll see you as you get out of the lockin (feel free to ping me via email if you've got anything specific).
Why drop autoscaling though? Note that you can use Autoscaling Groups with Kubernetes on EC2: https://github.com/kubernetes/contrib/blob/master/cluster-au... and the team would happily take bug reports (either as GH Issues or just yelling at them on slack/IRC).
(Sadly http://kubernetes.io/docs/getting-started-guides/aws/ doesn't point to this...)
Re:Docker in Production: A History of Failure
by user5994461 on Saturday November 05, 2016 @05:51PM
(#12882095)
It seems that doing auto scaling or doing kubernetes may take similar amount of work (in our current state of affairs). We want kubernetes on the long term so we might as well go straight to it.
I suppose that auto scaling will be back on the table later, to auto scale kubernetes instances. Maybe.
We have stuff that must stay on AWS, too dangerous to make a move now :(
We'll ignore the "switch to auto scaling" bit. Teammates have already started testing CoreOS & Kubernetes (on AWS) while I was writing the article. We'll figure it out and get it in production soon, hopefully.
We have a subsidiary which has no locking on AWS and could use an infra refreshing. They already have google accounts and use one or two products. They'll be moved to GCE in the coming months, hopefully.