4 ms·
I kind of don't understand why people don't use managed K8's and avoid needing to pay ops people to manage their setup. One can learn the developer side of K8'
by nickthemagicman 6y ago
I kind of don't understand why people don't use managed K8's and avoid needing to pay ops people to manage their setup.
One can learn the developer side of K8's in a week or so enough to be deploying apps and setting up services and pods without the overhead of managing etcd and distributed clusters.
- throwaway201103 6y agoWhen your site or app goes offline it can be handy if you have ops people who understand your setup.
- OJFord 6y agoIf EKS goes down it doesn't help its users nor AWS for its ops people to know how your webapp's configured.
- area51org 6y agoSetup = a k8s service? You should have support from the vendor, period. Setup = rep groups, internal services, etc? You need k8s-savvy ops people, or really good devs who like ops stuff.
- threeseed 6y ago> You need k8s-savvy ops people, or really good devs who like ops stuff They are called DevOps Engineers and it's a standard role these days. And it doesn't matter whether they like it or not. In many organisations these days developers own their piece of work all the way through to production and are expected to provide an ops-like support for it.
- deleted 6y ago[deleted]
- Townley 6y agoI use managed k8s, but have sympathy for the bare metal folks. Wiring servers together using kubeadm is so simple and powerful that the missing pieces of the puzzle (networking and storage, for example) feel frustratingly close. In an ideal world, you could purchase or rent commoditized resources (compute, storage, bandwidth) and have those resources deploy your application in a standardized way. K8s is so close to that out of the gate, that having to use cloud provider's expensive and proprietary offerings feels sub-optimal. I agree that cloud offerings are the way to go for anyone without good reasons not to (eg compliance, lack of connectivity, or full control over upgrades). But a lot of the "I prefer on prem" attitude comes from realizing that having a black box of an ingress controller on my cluster isn't the end state of how apps get deployed
- dilyevsky 6y agoFor prod? You’ll know when your gke control plane goes down and support is twiddling their thumbs for two days
- area51org 6y agoDoes that actually happen with GKE? If so: do not use GKE. Other vendors surely have better-supported k8s services.
- tcoff91 6y ago2 days of downtime from a GCP service? I didn't know the outages with these cloud services were ever that bad.
- dilyevsky 6y agoTwo days is nothing. I had their fabric black holing packets for weeks before it got fixed
- nickthemagicman 6y agoThis could be said about ANYthing in the cloud though
- dilyevsky 6y agoAbsolutely, anything vendored out even.
- area51org 6y agoIt really depends on what your needs are and whether your provider's k8s service addresses them. AKS for example does work but, I'm told, is missing some fundamental stuff in regards to security etc. (Caveat: I only know this through others.) OTOH if a service is available and would work for someone's use case, by all means, use the service. I've set up native k8s clusters just as exercises, and it's no picnic–and I didn't need to manage those clusters, later. Just doing build exercises alone was enough to scare me straight.
- vorpalhex 6y agoManaged k8s doesn't mean you don't need ops people. You still need ops people - you are still running a complex and customized multi-node kubernetes cluster. You just need fewer ops people by following a vendors optimistic path.