Re:Why Does Developing on Kubernetes Suck?
by tutfbhuf on Friday August 23, 2019 @07:25AM
(#20776364)
> It doesn't help when a service is only for few million users with few hundred or thousand containers.
Well my company switched from VMs to k8s (few hundred containers) and it helped. Proof me wrong.
My company switched from VMs to a managed k8s cluster (gcloud). It made everything harder, the application became about 5x slower and instead of a $300 monthly bill we paid for the VMs now we pay $1300.
So in summary:
* we still have same amount of developers
* we still need same amount of sysadmins
* we introduced more complexity
* the application became slower
* the whole thing became much more expensive (managed k8s price, education, consulting, etc.)
* but! we have the same amount of income every month. Surprisingly our users don't pay more for the same service because we run our stuff on k8s
Re:Why Does Developing on Kubernetes Suck?
by dragonsh on Friday August 23, 2019 @10:24AM
(#20777949)
Cannot comment on it unless see it in details that adding additional moving components of k8s helped.
Do you manage Kubernetes, personally? Did you manage the VMs?
Re:Why Does Developing on Kubernetes Suck?
by tutfbhuf on Friday August 23, 2019 @08:05AM
(#20776609)
Yes, i'm a DevOps engineer. I have to say, we use the Google Cloud and many Google Services, this makes live so much easier. Before that we managed everything ourselves on bare metal with debian VMs.
K8s is developed to manage large number of service nodes running docker or oci containers coming from Google borg project. So it was designed for managing google level of service loads. It doesn't help when a service is only for few million users with few hundred or thousand containers. LXD and traditional tools can already do it without learning new way with lots of moving parts.