Automatically rotate Docker Swarm secrets with Docker-sdp | Hacker News Reader

Automatically rotate Docker Swarm secrets with Docker-sdp

github.com

11 pointsancieque8 comments

Interesting to see something new being made for Docker Swarm! In my mind, it's still one of the easiest ways to get started with container orchestration, before eventually moving to something more serious (if at all needed): Docker Compose --> Docker Swarm --> Nomad/Kubernetes.

Being able to use the Compose specification (https://docs.docker.com/compose/compose-file/) both on single nodes with Docker Compose and then also across clusters with Docker Swarm is such a nice idea.

This tool is a really simple layer around docker stack deploy that caused us some headaches for automation.

We are building our internal tooling and app deployments around Docker Swarm if possible due to the low barrier for entry. Clustering concepts stay the same anyways once we need to switch.

And while we are doing so, we take older tutorials and versions for swarm and modernize them on our GitHub. For example, see our modernized swarmprom here: https://github.com/neuroforgede/swarmsible/tree/master/envir...

Why? It’s a bit like building for Betamax after VHS has won.

It works and is simple.

It’s an overly simplistic facade on top of a complex problem, and that facade quickly breaks down. Also for all intents and purposes it’s dead - a smattering of commits in the last two years.

SSH + “make deploy” is simple and it works. It doesn’t mean it’s a good idea or you’ll be able to hire for it in a year or two.

It does what it should for us.

SSH + "make deploy" is a really bad comparison as you don't get overlay networking for free and also don't get any HA.

What we need:

1. HA for services 2. networking between nodes 3. ingress into the cluster 4. possibly volumes

All 4 are solved to our liking. Once we really need Kubernetes, we can do the switch.

> All 4 are solved to our liking. Once we really need Kubernetes, we can do the switch.

Indeed, but this still doesn't mean it's a sound technical decision to build a bunch of custom tooling ontop of a dead and soon unsupported foundation that very few people use then realize too late that switching to a supported platform isn't as easy as you'd have hoped.

I'm not comparing Swarm to Kubernetes, that's been done to death, I'm merely pointing out it's odd that you're spending time and energy building commodity features that already exist in k8s and are not core to your product.

Good luck though!

docker-stack-deploy is not adding too much, and I don't see it doing much more in the future.

But I get your point and believe it is in good faith, so thank you for your thoughts :).

Reply on news.ycombinator.com