Live data from Hacker News

The demise of Docker and the rise of Kubernetes

thehftguy.com

51–60 of 101 posts

Re: The demise of Docker and the rise of Kubernetes

#51

And yet I still have to deploy my first Kubernetes setup and have used Docker multiple times ... Is there some kind of "Kubernetes-light" out there? So something like in-between running services like NGinx and Postgres on bare Linux machines and having this (I think complex) Kubernetes setup? It's important to say that I don't need any scaling capabilities (apart from maybe some load-balancing in case of a machine er…

Good point, there is still a barrier between how people deploy (kubernetes) and how people develop (docker-compose). And it's not just different syntax, developers typically never have to deal with concepts like ingress and persistent volume claims. Things like converting compose to k8s manifests don't really help developers to understand how kubernetes works in production. As a result, Kubernetes tends to help to reinforce the need for ops people, for better or worse.

Re: The demise of Docker and the rise of Kubernetes

#53
post #12

And yet I still have to deploy my first Kubernetes setup and have used Docker multiple times ... Is there some kind of "Kubernetes-light" out there? So something like in-between running services like NGinx and Postgres on bare Linux machines and having this (I think complex) Kubernetes setup? It's important to say that I don't need any scaling capabilities (apart from maybe some load-balancing in case of a machine er…

I would give Nomad a try. After reading pages on pages of Kubernetes setup and trying the many half-working setup tools de-jour, setting up Nomad was a breeze and keeping it running over many months took almost no effort at all. URL: https://www.nomadproject.io

Nomad is great, and easier to grasp than Kubernetes, and with Consul you also have have DNS-based service discovery for your Nomad programs.

Re: The demise of Docker and the rise of Kubernetes

#54
post #10

Earlier quoted context omitted.

easiest way is just start experimenting with GKE on google cloud, and see if it has value to you. Don't bother trying to deploy and manage it before you've kicked the tires. Out of the box its quite good, depending on what you are doing, once you have cert-manager issuing you free certs, linkerd managing a service mesh, and stackdriver giving you an entire ops stack, its a bit hard to go back

How big is the vendor-lockin though? Let's say I want to use both Hetzner Cloud and GCP instances - I am sure it's possible, but the question is how much of a hassle it is ...

If you want to use both then you should investigate rancher - that's the problem they're trying to solve.

Re: The demise of Docker and the rise of Kubernetes

#55
post #13

Kubernetes is a thick, complex wrapper around deploying Docker applications.

That's my impression too. Kubernetes and Docker work very well together, so Docker knowledge is not out of date. It's just that Kubernetes is now relevant too. And more in demand because fewer people are fluent in it yet.

Re: The demise of Docker and the rise of Kubernetes

#56

And yet I still have to deploy my first Kubernetes setup and have used Docker multiple times ... Is there some kind of "Kubernetes-light" out there? So something like in-between running services like NGinx and Postgres on bare Linux machines and having this (I think complex) Kubernetes setup? It's important to say that I don't need any scaling capabilities (apart from maybe some load-balancing in case of a machine er…

learning kubernetes here too. helm seemed to be the answer but...

i spent hours trying to make helm work on my mac and in the end gave up. the original error was with comparing floats in the latest version. that error seems to pop up every now and then in their issues list. now, there is no way to install an earlier version. not with brew anyways. installing from binaries or sources is nightmarish. and when you do, it might not like your minikube setup. and yaddi yaddi yadda...

it feels odd and strange to me that the trend nowadays is to accept these complicated systems and be amazed by how complicated they are...

Re: The demise of Docker and the rise of Kubernetes

#58

Earlier quoted context omitted.

Not even docker, mostly AWS or dedicated servers or even VPS... No small site needs kubernetes/docker orchestration and that's fine.

Docker isn't just for orchestration. I've used it in a very small company and even use it for personal project just because it provides me with an easy to set up and portable development environment.

For my small personal projects, xampp is sufficient.

Re: The demise of Docker and the rise of Kubernetes

#59
post #13

Kubernetes is a thick, complex wrapper around deploying Docker applications.

My opinion: Kubernetes is a simple wrapper around Docker containers, that has a tremendous number of gotchas. The overall concept is pretty simple: You create a deployment that spins up pods which are your containers. You create ingress and services to direct traffic to the pods. You configure it all with environment variables through ConfigMaps and Secrets. However, there are still so many one-line commands you need…

Virdings law...

Re: The demise of Docker and the rise of Kubernetes

#60
post #44

I'm not particularly fond of Docker but I don't see it going away any time soon. I acknowledge there has been alternatives around which were better in some aspects than Docker yet haven't worked in a single company that didn't use Docker with Kubernetes or other orchestrators (e.g. AWS ECS). Not saying they don't exist, but it's very rare on my experience (both as fte and as a consultant). Also I have never met a ded…

It would be worrying if something as basic as Docker required an expert's worth of arcane procedures, workarounds, tricks, ancillary tools and so on.

In my experience Docker is almost as trouble-free as it should be, with straightforward tools to make mistakes and undo them; it requires good engineers who know what they want, not wizards who know how to get it.

Post reply on HN