Yes. Exactly. Kubernetes is adding complexity needlessly. People are so dumb, they can't understand that more isn't always better.
Kubernetes for personal projects? No thanks
91–100 of 278 posts
Re: Kubernetes for personal projects? No thanks
#92> Do you want to do all of this because you think is fun? Or because you want to learn the technology? or just because? Please, be my guest! [...] Kubernetes is likely here to stay. If you're interested in running a cluster to undestand what the hype is all about and to learn something new, you should do it. Also, ignore everybody telling you that this platform wasn't meant for that. Complexity is a weak argument. On…
> just write a couple of manifests to deploy a project, versus...
Whenever anyone says "just do something" these days, it usually means that it hasn't been thought through properly. Is that only my personal experience?
Re: Kubernetes for personal projects? No thanks
#93I don't even want to use it for commercial projects. It needs a certain scale before the overheads are worth it.
Didn't expect this comment to come back from being voted down so much! Guess it splits opinion.
Re: Kubernetes for personal projects? No thanks
#94Earlier quoted context omitted.
I have to disagree. It doesn't introduce burden and complexity. They're already there whether you use Kubernetes or not. The difference is that if you did build it all by hand as the author said, if it ever scales, you're going to have double the job to make it scale. It's all a question of: do I think my software will succeed? If it's a hobby project that will never get big, it's not worth the hassle. If it actually…
Let's talk about complexity for a moment, for one aspect of a simple service: ingress. Kubernetes: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: test-ingress spec: rules: - http: paths: - path: /testpath backend: serviceName: test servicePort: 80 Nginx: location /testpath { proxy_path http://127.0.0.1:8080 } Which is less complex? Which is beta, and thus could be changed over time (it happens a lot). W…
The first one is a complete configuration you could kubectl apply into a cluster that sends traffic to a backend service that may be running across multiple instances on multiple machines.
The second is a configuration fragment that is useless by itself that would send all traffic to a single instance running on localhost.
Re: Kubernetes for personal projects? No thanks
#95I totally agree with this article. I'm giving a point of a view of a pure developer who knows nothing about DevOps things and managing servers. I kind of know what NGINX is and barely know how to configure something like systemd. I recently setup a digital ocean droplet and setup my blog there to actually understand how it works. It was great because I learned a ton and feel in control. Pretty simple setup - single d…
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.
Re: Kubernetes for personal projects? No thanks
#96Earlier quoted context omitted.
Let's talk about complexity for a moment, for one aspect of a simple service: ingress. Kubernetes: apiVersion: extensions/v1beta1 kind: Ingress metadata: name: test-ingress spec: rules: - http: paths: - path: /testpath backend: serviceName: test servicePort: 80 Nginx: location /testpath { proxy_path http://127.0.0.1:8080 } Which is less complex? Which is beta, and thus could be changed over time (it happens a lot). W…
The first one is a complete configuration you could kubectl apply into a cluster that sends traffic to a backend service that may be running across multiple instances on multiple machines. The second is a configuration fragment that is useless by itself that would send all traffic to a single instance running on localhost.
You can just drop it in a conf.d folder created by the package install and it would work just fine.
Also we're talking simple projects, and simple projects are typically not distributed; typically don't need to be distributed.
That said, supporting multiple backends with different load balancing algorithms is also pretty simple to write as well.
Re: Kubernetes for personal projects? No thanks
#97I absolutely love docker for development. It saves so much set up time, and of course is handy later.
Re: Kubernetes for personal projects? No thanks
#98Earlier quoted context omitted.
"If you are on Kubernetes, then you are not locked in to any cloud provider" ...but I would be beholden to GNU/Linux and have to do the same thing I do with SmartOS in a far more complex way, built on an operating system substrate which cannot provide the reliability that I need to be able to sleep through my nights without an incident. Kubernetes, Docker, Linux are a time sink that I can never get back, on things wh…
> the same thing I do with SmartOS in a far more complex way Citation needed. Yes, Kubernetes runs on Linux kernel and until someone ports it to use something other than iptables and the linux cgroups API, that will be true. But I could say the same thing about being locked into SVR4/OpenSolaris, and I bet you a Coke that a lot more people will agree with me. The Kubernetes slack community has over 48,000 members and…
Don't waste your time, he's a troll that pops up on every thread that has anything to do with things like docker or k8s. It doesn't matter what the problem is, smartos is the solution.
SmartOS is solid technology, but he doesn't have the slightest clue what k8s does, but is completely certain that smartos somehow does "the same thing" better.
They aren't even mutually exclusive, there's no reason you couldn't write a CRI backend to run k8s on top of zones on smartos.
Re: Kubernetes for personal projects? No thanks
#99Earlier 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…
I didn't fail, I just couldn't see a strong ROI after doing a spike. I did use kubeadm. It required considerably more than just 3 simple steps required to get a basic working cluster up. Two days was more like it.
Re: Kubernetes for personal projects? No thanks
#100Oh man, the original article went way over the author's head. The point of the original article was that even though Kubernetes is primarily useful for tackling the challenges involved with running many workloads at enterprise scale, it can also be used to run small hobbyist workloads at a price point acceptable for hobbyist projects. Does that mean that Kubernetes should now be used for all hobbyist projects? No. If…
Doing a small project is a best way to learn a new system. If you never plan to use Kubernetes then I would agree, why would you use it at all? But if you're exploring it there could be no better way to get your feet wet than with a small project.