Why is Kubernetes getting so popular?

Post by tapirl » Sat, May 30, 2020, 4:24 PM UTC

eyberg wrote: post #596

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…

> Company saves money by not having to hire Linux sysadmins Citation? In my experience companies hire more sysadmins when adopting k8s. It's trivial to point at the job reqs for it. > Company saves money by not having to pay for managed cloud products if they don't want to Save money?! Again citation. What are you replacing in the cloud with k8s? In my experience most companies using k8s (as you already admitted) don…

Post by p_l » Sat, May 30, 2020, 4:29 PM UTC

jrumbut wrote: post #499

rocho wrote: post #468

Earlier quoted context omitted.

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.

In a world where your architecture is that simple I don't think kubernetes would be the choice for long. I think for the average application there's still something to be said for manual cross-layer optimization between infrastructure, application, and how both are deployed. What I mean is we can't yet draw too clear a line between the application and how it's deployed because there are real tradeoffs between keeping…

Post by pjmlp » Sat, May 30, 2020, 4:36 PM UTC

toyg wrote: post #478

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…

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…

Post by CyanLite2 » Sat, May 30, 2020, 4:43 PM UTC

zelly wrote: post #529

rocho wrote: post #468

Earlier quoted context omitted.

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.

Kubernetes is for orchestrating a distributed system. What I was suggesting is to (1) make a monolith and (2) make it fast, light and high-throughput. The goal of your service is to reliably serve users at scale; this is just another way of doing it, just much more esoteric. A "C++ monolith" allows me to potentially bypass a lot of this deployment stuff because it could serve lots (millions) of users from a single bo…

Post by p_l » Sat, May 30, 2020, 4:44 PM UTC

fock wrote: post #585

jordic wrote: post #560

Earlier quoted context omitted.

Do you manage to aggregate all logs on a single place? Do you have the same environment as staging? How do you upgrade your servers? Do you have multiple teams deploying on their own components? Do you have a monitoring/metric service? How do you query the results of a Cron? Can you rollback to the correct version when you detect an error at production?

remote syslog has been a thing for how many years?! As has using a standard distribution for your app with a non-root-user for each app, easily wiped and set up every deploy (hint: that's good for security too!). Monitoring was also a solved problem and I guess Cron logs to syslog. Rollback works just like a regular deploy? (I wonder how good k8s helps you with db-schema rollbacks?)