Kubernetes for personal projects? No thanks

Post by acjohnson55 » Thu, Oct 04, 2018, 3:45 PM UTC

falcolas wrote: post #71

shaklee3 wrote: post #66

Earlier quoted context omitted.

This doesn't make sense, and it's really the opposite of what you're saying. K8s is hard, but for large scale you need something robust that's tested at that scale. A collection of shell scripts is more like a beginner tool set. Yes, it's easy to learn, but it will break when you get serious.

For large scale you have to first make your application capable of scaling. That's a bit that's missing from most of these conversations. Only the simplest programs can "scale up" by just adding more programs - most have to be re-architected to move all the state in the program to some other service. That is to say, if scaling is your primary concern, you have a dozen other things more important to fix than your choi…

Post by acjohnson55 » Thu, Oct 04, 2018, 3:47 PM UTC

collyw wrote: post #95

parasubvert wrote: post #38

Earlier quoted context omitted.

There’s been a bit of a full circle going on in the industry. PaaS like Heroku were rejected by many because they couldn’t tinker inside the box. Docker and Kubernetes changes that, and there will be new Heroku-like experiences built on them. But for now we are in this weird mode where the Kubernetes momentum is eclipsing even Docker, even though raw K8s reminds me of Linux in the Slackware days. there is so much FOM…

As someone that knew how to set up a server before hand I found Heroku a real pain in the arse to use.

Post by justinsaccount » Thu, Oct 04, 2018, 3:50 PM UTC

falcolas wrote: post #109

justinsaccount wrote: post #102

Earlier quoted context omitted.

Ok, great... I have a bunch of simple projects like that, one web instance running on a single host. How do I safely upgrade it without downtime? Ensuring that the new version starts up properly and can receive traffic before sending it requests and stopping the old one? With k8s: kubectl set image deployment/my-deployment mycontainer=myimage:1.9.1 (or just use kubectl apply -f) With your nginx config: ????

That moves the goalposts a bit. We've gone from a simple service to a fleet of highly available services on multiple hosts with zero downtime requirements. At which point, sure, use Kubernetes.

Post by jkmcf » Thu, Oct 04, 2018, 3:59 PM UTC

colonelpopcorn wrote: post #79

y4mi wrote: post #75

Earlier quoted context omitted.

i set up a kubernetes cluster 1 year ago at work and a private one last weekend. last year took, i think 2 days. my private one was up and running within ~1h, including writing the ansible role to first install binaries/dependencies and join the cluster as a worker node. either you didn't use kubeadm to set it up or ... i have no idea how you could've possibly failed. its pretty much (all) ${packagemanager} install d…

Jeff Geerling even wrote an Ansible role to do all of the heavy lifting for you. I've used it alongside vagrant to spin up a three node cluster in ~15 minutes. https://github.com/geerlingguy/ansible-role-kubernetes

Post by collyw » Thu, Oct 04, 2018, 4:02 PM UTC

acjohnson55 wrote: post #113

collyw wrote: post #95

Earlier quoted context omitted.

As someone that knew how to set up a server before hand I found Heroku a real pain in the arse to use.

To learn, or to utilize on an ongoing basis? I'm curious what you found difficult, because since remapping my mind to 12-factor years ago, I still haven't found anything as simple as just using Heroku.