“You don’t need Kubernetes” Until... Your boss asks you to setup your entire application stack for local development... lol good luck with that, should have used Kubernetes (check out the Kind project). /2
-
-
Prikaži ovu nit
-
“You don’t need Kubernetes” Until... You find yourself using Chef, Ansible, Puppet, and bespoke bash scripts to inject configuration files and environment variables... should have used Kubernetes. /3
Prikaži ovu nit -
“You don’t need Kubernetes” Until... You need to add health checks to your applications, and every application runs their health check server on a special port and endpoint, so you have to write a special bash script for each one.. should have used Kubernetes. /4
Prikaži ovu nit -
“You don’t need Kubernetes” Until... You’re not sure why your legacy PHP application crashes randomly so you write a special bash script that restarts it when that happens... should have used Kubernetes. /5
Prikaži ovu nit -
“You don’t need Kubernetes” Until... You want to restrict the CPU usage of your app so it doesn’t freeze up your host when load is high and on a Friday night you find yourself googling Linux cgroups.. should have used Kubernetes. /6
Prikaži ovu nit -
“You don’t need Kubernetes” Until... You find yourself manually replacing a 1000 node ec2 autoscaling group AGAIN cause you made a typo in one of the config files, lol should have used Kubernetes. /7
Prikaži ovu nit -
“You don’t need Kubernetes” Until... You’re asked to build a MySQL database... lol yeah don’t use Kubernetes (yet). /8
Prikaži ovu nit -
I don’t know about y’all, but at least one of the above has been true in every company I’ve worked for. And yes we always ended up using Kubernetes and didn’t regret the complexity trade-off cause it’s not nearly as complex as our own tools that address the same problems.
Prikaži ovu nit -
People replying "just do X instead" are misunderstanding the point of this thread. I'm not saying Kubernetes is a silver bullet, but to say "it's probably not needed" or "it's too complex" without fully understanding its trade-offs w.r.t someone's use-case is pretty ignorant.
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
And who's resizing the VMs you're running your Kubernetes in?
-
With a managed Kubernetes you would, ideally, just add more node pools and delete the old node pools. CSI backed volume mounts will follow the pods as the deployment shuffles them to new nodes. That said, resize+reboot of existing VMs seems equally simple yet risky.
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

