Why is Kubernetes getting so popular?

Post by howox » Sat, May 30, 2020, 10:15 AM UTC

Multicomp wrote: post #517

pas wrote: post #509

Earlier quoted context omitted.

There are quite a few GUI tools for k8s. Currently mainstream k8s is text based, because it's still too fast moving and new. Creating a great GUI would be a serious overhead and there's not enough interest/demand for it. It'll come eventually.

Rancher does a lot of the orchestrating of k8s clusters and works well in my experience.

Post by fxtentacle » Sat, May 30, 2020, 10:17 AM UTC

Perseids wrote: post #475

tutfbhuf wrote: post #469

Earlier quoted context omitted.

I can see your point for small hobby projects. But enterprise web development in C++ is no fun at all. For example: "Google says that about 70% of all serious security bugs in the Chrome codebase are related to memory management and safety." https://www.zdnet.com/article/chrome-70-of-all-security-bugs... Developer time for fixing these bugs is in most cases more expensive, than to throw more hardware at your software…

True, but the alternative to C++ with that reasoning is Rust or Go (depending on your liking), not Ruby. And with both of these you can step around a lot of deployment issues, because a single server can be sufficient for quite high loads. Avoid distributed systems as much as you can: https://thume.ca/2020/05/17/pipes-kill-productivity/

Post by fxtentacle » Sat, May 30, 2020, 10:21 AM UTC

Perseids wrote: post #488

toyg wrote: post #478

Earlier quoted context omitted.

Rust and Go could help you there, and their deployment story is as excellent as C/C++: just compile and ship. However, their learning curve is pretty steep (particularly Rust) and most developers don’t enjoy having to worry about low-level issues, which makes recruitment and retention a problem. Whereas one can be reasonably proficient with Python/Ruby in a week, Java/C# is taught in school, and everyone has to know…

Do those highly available developers have the same quality as the Rust developers you could get, though? (On average.) I'd wager there is a correlation between interest in deeper topics as required by Rust and good long term design and quality. I've seen how marvelously efficient a small team of very talented people can be be. To replace them with the average highly available developers you would need far more than d…

Post by Multicomp » Sat, May 30, 2020, 10:23 AM UTC

verdverm wrote: post #497

aprdm wrote: post #150

Earlier quoted context omitted.

Not necessarily. You can have all of above with Terraform, Ansible, Puppet, Chef... etc.

Instead of a varied interface tools set, I can have one with consistent interfaces and experiences. Kubernetes is where everything is going, hence why TF and Ansible have both recently released Kubernetes related products / features. It's their last attempt at remaining relevant (which is more than likely wasted effort in the long run). They have too much baggage (existing users in another paradigm) to make a success…

Post by zelly » Sat, May 30, 2020, 10:34 AM UTC

rocho wrote: post #468

zelly wrote: post #394

Main benefits of Kubernetes: • Lets companies brag about having # many production services at any given time • Company saves money by not having to hire Linux sysadmins • Company saves money by not having to pay for managed cloud products if they don't want to • Declarative, version controlled, git-blameable deployments • Treating cloud providers like cattle not pets It's going to eat the world (already has?). I was…

I don't agree with the last paragraph. Your C++ example is orthogonal to the deployment aspect because it discusses the application. Kubernetes and the fragile shell scripts are about the deployment of said application. How are you going to deploy your C++ application? Both options are available, and I would wager that in most cases, Kubernetes makes more sense, unless you have strict requirements.