4 ms·
The problem with Kubernetes seems to be one of knowing when to make the switch. My company is in a place where I think k8s would be really beneficial. We are
by cogman10 6y ago
The problem with Kubernetes seems to be one of knowing when to make the switch.
My company is in a place where I think k8s would be really beneficial. We are at the 40k VMs running 1000 different types of apps. We suffer from tremendous wasted resources as a result.
The company started before k8s (and even docker) were things. So getting us there seems like a real daunting (yet worth it) task.
So, we are left with sort of a chicken/egg problem. It would have been unreasonable to start with k8s, yet now it is a huge cost to switch to it (even though it will save us millions).
- brown9-2 6y agoIt’s easy to overestimate that you’ll save money here - if you have waste, poor cost attribution, etc., you can easily do the same with Kubernetes managing the nodes and scheduling the processes. To actually save the money you have to fix those things first.
- cogman10 6y agoThe issue we have is that we are a very peeky computation requirements (not a steady stream of calculations going on). Further, we've got a fairly deep data processing pipeline. It's not unusual for us to see high loads on early parts of the system 1 hour and 1 hour later seeing high loads on the later parts of the system. Unfortunately, we don't currently have a way to scale out and reassign resources. That means we've built out for our peaks even though the majority of the time that hardware is sleeping. We could spend the time building out a scaling system (right now, our resources are all on prem). However, why do that when we can instead take advantage of k8s already built in scaling capabilities? So, technically not k8s that will be saving us money, but rather implementing autoscaling. However, the solution with k8s is really nice.
- brown9-2 6y agoCluster autoscaling with nodes on-prem, or in the cloud?
- exhilaration 6y agoI work for a large Unnamed Parcel Service and all of our future applications are going to Azure Kubernetes Service, which is the Microsoft-managed k8s offering. There are still a ton of legacy applications running on all sorts of platforms, from mainframe to just about any technology you can name from the past 40 years, but everything going forward is being written for .Net Core running on Linux containers in AKS. So you don't have to switch everything immediately, you can get around to it eventually but at least you can start to build up a pool of talent and skill set towards that goal.