4 ms·
Microsoft Word is also incredibly complex software with decades of development and features, and yet it's just a word processor. Everyone uses a small subset of
by manigandham 8y ago
Microsoft Word is also incredibly complex software with decades of development and features, and yet it's just a word processor. Everyone uses a small subset of the actual functionality which is why the entire system can be complex and simple at the same time, depending on your needs.
It's exactly the same with Kubernetes. It's just clustering software that ties multiple servers together to give you an PaaS-like workspace to run containers, but there are 1000s of details you can use if you need them to build much more intelligence into operations. If you don't need them, you can just run a single container and still benefit from simple declarative deployments and automated oversight.
- MBCook 8y agoBut it’s trivial to start typing in Word. Spell checking is easy, as are basic formatting operations. Loading/saving work the way you’d expect. Yes you can write a dissertation with a ton of support from Word to make you life easier, but doing simple things is simple. It sounds like that’s what missing from kubectl. Even for a small start it takes a lot of knowledge. To continue the Word analogy, that sounds like LaTeX. It’s very powerful, but no normal person is going to get started for the first time very fast for basic tasks. Certainly not compared to Word. The Rails analogy from the article seems very apt.
- tootie 8y agoIt's true and I think that there's a base case for orchestration that is to autoscale nodes based CPU/memory consumption behind a load balancer that would get 90% of projects off the ground without needing to think about yaml files.
- manigandham 8y agoDoing simple things in Kubernetes is also simple. It's 1 line to get a pod up and running: kubectl run appname --image=yourimage You can then graduate to a basic YAML config file with a few lines and update with: kubectl apply -f yourfile.yaml At some point, if you want to build a distributed application, you need to know the concepts involved. Looking at it relatively, you needed to learn and deal with many more low-level details before Kubernetes existed, so it's actually quite an improvement to what we had just a few years ago.
- vidarh 8y agoYou skip over setting up Kubernetes. And keeping it running.
- pas 8y agoA distributed system will never be as intuitive as MS Word, which is basically the digitized version of stone tables, or papyrus, or whatever thousands of years old thing we are already familiar with. Or just remain a bit more strict and look at typewriters. Word is a typewriter. People look at typewriters and sort of understand them after pushing one-two buttons. Yes, there are hidden gems and details and a long road from mechanical typewriters to Word and laser printers (e.g. https://www.youtube.com/watch?v=bRCNenhcvpw https://www.youtube.com/watch?v=bRCNenhcvpw ), but people are a lot more intuitive about these pieces of hardware and software, because they are simply updates on existing tech. Distributed systems is a new, and hitherto an explicitly unknown concept for many people. And with minikube you can set up k8s as easily as MS Office. (Or you can use Typhoon https://typhoon.psdn.io https://typhoon.psdn.io .. ) And it's trivial to package up all this into a website, like Office 365 and GKE https://cloud.google.com/kubernetes-engine/ https://cloud.google.com/kubernetes-engine/ . Or you can run it on your own PC with minikube and Virtualbox/KVM/qemu, and similarly you can install Office locally. But it does not make sense for one and it increasingly makes less for the other too.
- manigandham 8y agoIf we're talking about the actual installation of a distributed system, then installing a distributed database isn't "easy" either, and also requires knowing the concepts so you know what you're doing. Kubernetes is not going to be simpler or easier than the software that it's designed to run on top of itself, but it's not that hard anymore either. The installers work well, there are several distros with varying capabilities, or you can just use the public clouds like most where it's 1 button.
- discodave 8y agoCompare to setting up a Lambda application with a DynamoDB or Aurora database. Very simple, has limitations but you get a scalable distributed system for (almost) no time investment.
- pas 8y agohttps://cloud.google.com/kubernetes-engine/ https://cloud.google.com/kubernetes-engine/ .. easy as Office365. With GitLab you can deploy to k8s directly. Like Word and let's say SharePoint. Also, there are a lot of folks doing this commoditization and packaging up k8s in various ways to make it more usable for a wider audience. You're comparing k8s to Word instead of Windows kernel. Or maybe instead of .NET.
- barrkel 8y agoK8s changed the way I thought software should be built, because it presents the data centre as an API. K8s is also not that complicated after you grok it. It's also pretty easy to get started for simple cases. It's just that you need to switch your mindset a bit; but the benefits from the mental switch are non-negligble.
- drdaeman 8y ago> K8s is also not that complicated after you grok it. Writing (or code-generating) a bunch of YAML configs is the easiest part about K8s. Diagnosing why in the world it misbehaves in some weird manner is where the real complexity is. Of course, this does not apply when you're not a system administrator, but just an user of someone's else (Google) K8s.
- _5meq 8y agoYES. THIS!! I'm a single-person ops team for my startup. Granted, I MAY be an exceptional learner and not realize it, but I mostly consider myself an under-achieving stoner. I chose Kubernetes as our platform a few years ago and it's been absolutely wonderful and only getting better. Every once in a while I do a thought experiment with my co-workers to ensure Kubernetes is still the product for us. It is. We all love it and it makes my job easier. And it's really not that complicated. Let's go ahead and list a few things Kubernetes Provides at the cost of writing a few YAML files and provisioning some docker containers in our CI/CD stack: - Service discovery and health checks - Zero downtime upgrades with rollouts and rollbacks - Horizontal auto-scaling ( VM AND container ) - Configuration management and secret storage - Immutable infrastructure - Automatic SSL provisioning and routing via kube-lego and GCE ingress controller - Log aggregation and monitoring via Heapster - Cloud-provider agnostic configurations - A consistent and approachable API to implement required features onto. - ( With Google GKE ) Automatic security updates with a set maintenance window. - Easy deployments with Kubernetes Keel There are more benefits but these are the ones that come off of the top of my head. ALSO, it's an opinionated framework that makes doing things "The Right Way" easy and intuitive to do. In my TINY organization's reckoning, K8 actually makes our lives EASIER rather than more complicated and is considered one of the best decisions we ever made. It gets out of our way and lets us work on the fun stuff. > In the case of applications that simply don’t have the scale problem, they usually don’t need the added complexity of a self-healing, horizontally scalable system. If you build on a swamp your castle is going to sink into the swamp. Don't obsess over scale, but plan to scale, even if it's just "We can throw more servers at it." Self-healing? The author is correct: Probably not necessary. But scaling goes both ways: Our start-up is counting pennies and saving money wherever we can. Having an auto-scaling pod and node cluster makes so much sense. Our cluster automatically scales up and down based on load, saving us thousands of dollars a month. > The problem I see with Kubernetes is that the cognitive load in the early parts of a project are simply too high. The number of things you need to create and worry about are a barrier to starting a project and iterating on it quickly. In the early days of a project, feature velocity and iteration speed are the most important factors. I view the Heroku model as the ideal development model. You have a managed hosted Postgres database and you just git push to get new code deployed and out the door. There’s very little to think about. It may not scale to infinity and it may get expensive, but you can worry about those things once you’ve actually got a hit on your hands. I disagree with the assertion that starting out is difficult ( Or, that it is more difficult than other solutions ), and heroku is EXPENSIVE. With GKE, you are paying for the VMs and little more and get a BUCKET-LOAD more features. What is this nebulous "complicated part" of setting up kubernetes? You literally hit a button and it creates your cluster. You can have an application ready to go with three objects: a service, an ingress, and a deployment. I find Heroku to be of a similar complexity with less flexibility. I get EXCELLENT monitoring and log aggregation by running `helm install datadog` and providing my key. I get a good-enough rabbitmq cluster by calling `helm install rabbitmq`. I get automatically provisioned SSL by calling `helm install kube-lego.` So I suppose my response would be: No, I don't think it will. I think the complexity is over stated.
- itomato 8y agoWhen things go wrong in Word, there's no need (or potential) to dig into the underlying code for analysis.
- manigandham 8y ago...Ok? I don't see the point though.