3 ms·
No kubernetes will be a bad choice for your use case. But if you learn all the intricacies and manage a behemoth besides your own application it will help in yo
by dragonsh 7y ago
No kubernetes will be a bad choice for your use case. But if you learn all the intricacies and manage a behemoth besides your own application it will help in your resume to brag that you are a modern devops and a fashionable one using kubernetes.
If you need a practical suggestion use simple solution like LXD [1]. But as you are already using docker stay with it and ansible.
As you are using ansible you are already doing infrastructure as a code, you are way ahead of curve already.
Probably when you grow a bit bigger use packer [2] and terraform [3], but I think ansible will do just fine.
Kubernetes was designed for Google kind of problem the burden to maintain is quite high with lots of moving parts, unless you use Google GKE or Amazon or managed kubernetes service. So don't fall for it unless you need it for your resume.
[1] https://linuxcontainers.org/ https://linuxcontainers.org/
[2] https://www.packer.io/intro/ https://www.packer.io/intro/
[3] https://www.terraform.io/ https://www.terraform.io/
- samvher 7y agoGKE and EKS are very expensive which in my opinion makes using them unattractive for smaller scale projects. But Digital Ocean now offers managed Kubernetes for free, I've played around with it and it actually seems really easy to set up and manage. Would be great if the competition would follow suit.
- jorams 7y ago> GKE and EKS are very expensive > Digital Ocean now offers managed Kubernetes for free GKE is just as "free" as DO, in that you only pay for the nodes you actually use (those nodes are probably a bit more expensive, admittedly). EKS is the outlier in this trio in that you also have to pay (a lot) for the master. Could you clarify what GKE could do to "follow suit"?
- samvher 7y agoIt seems, nothing! I was just wrong about GKE being expensive, not sure why I thought that (though it seems that until late 2017 they did have costs per cluster).