I Almost Ditched k3s for Docker Swarm (And Why I Didn't)

After two years of k8s complexity, I seriously evaluated switching to Docker Swarm. Here's what I learned about the trade-offs and why I ultimately stayed.

Ștefan Muraru
@ChrisRichner I am in a very similar situation and currently building a docker swarm cluster. As a replacement for argocd I found swarm-cd. It's by far not argocd but the main function, deploying from git, is there.
https://github.com/m-adawi/swarm-cd
It also supports encryption of docker secrets via sops.
https://github.com/madic-creates/swarm-git-ops
GitHub - m-adawi/swarm-cd: SwarmCD: Declarative GitOps and Continuous Deployment tool for Docker Swarm.

SwarmCD: Declarative GitOps and Continuous Deployment tool for Docker Swarm. - m-adawi/swarm-cd

GitHub
@ChrisRichner At the beginning I was sure I need to replace k3s with swarm to reduce complexity. But now I am not sure anymore. Though I haven't arrived the point yet, to stay with k3s 😅
@Madic Da ich nicht auf ein angezähltes Pferd setzen möchte, habe auch ich damit gestartet #k3s im #HomeLab hoch zu ziehen 🚀 Fühlt sich nach massivem #overengineering an, macht aber Freude wenn die „Enterprise Tools“ mal rund laufen 😉