3 ms·
I've worked for a number of enterprise companies. All have moved to Kubernetes. And it's not just geekery by developers who aren't as smart as you. It's becau
by threeseed 3y ago
I've worked for a number of enterprise companies. All have moved to Kubernetes.
And it's not just geekery by developers who aren't as smart as you.
It's because it allows you to treat all of your infrastructure in one way. Whether you are on GCP, AWS or On-Premise, whether you use Java, Spark, Web Serving or ML Training, whether you are deploying direct to Production or go through multiple staging environments etc. It is always one way of deploying things, one way of securing things, one way of doing everything.
It is far cheaper, easier, more secure and less risky than managing infrastructure yourself. And believe me we all tried that.
- MajimasEyepatch 3y agoSeriously. People make Kubernetes out to be this wildly complicated technology, but if your environment is more complex than just "Here's a glorified VM running on a couple EC2 instances behind a load balancer," it has a lot of benefits and is really not that difficult to set up in this day and age.
- wg0 3y agoThose who think Kubernetes is simple and easy and not complicated at all do most likely only fall in two categories: a. Someone else is running Kubernetes for them. (GKE, EKS etc) b. Or they're not running Kubernestes in production yet. (Homelab, staging prototype etc.) So yes from the point of view of it's APIs and it's object model, it's not complicated. EDIT: grammar
- tryauuum 3y agoDo you run VMs inside kubernetes as well? I know this is possible but wonder how's the actual experience