docker-volume-hetzner VS honey-swarm

we use https://github.com/costela/docker-volume-hetzner which is really stable.

CSI support for Swarm is in beta as well and already merged in the Hetzner CSI driver (https://github.com/hetznercloud/csi-driver/tree/main/deploy/...). There are some rough edges atm with Docker + CSI so I would stick with docker-volume-hetzner for now for prod usage.

Disclaimer: I contributed to both repos.

The big one which would be nice: CSI support. This is currently being worked on, though. This said the current volume plugin landscape is not that dire once you realize that the local volume driver which arguably has a confusing name can work with NFS,CIFS,etc. out of the box as long as you can use fuse mounts. Besides that, we are quite happy with our setup where we use the community volume driver for our cloud provider - https://github.com/costela/docker-volume-hetzner/

6. Volumes: Hetzner Cloud Plugin, see https://github.com/costela/docker-volume-hetzner

Reasons that we would dabble in k8s again:

1. A lot of projects are k8s only (see OpenFaaS for example)

I've been using docker swarm + traefik + portainer and I'm quite happy. I orchestrate everything with Ansible [1]. The only manual process I have is provisioning the servers / load balancers.

It provides a super nice balance between going all manual VPS and going all on the kubernetes cool aid

[1] https://github.com/sergioisidoro/honey-swarm

I moved to CapRover, and shortly after ended up moving to Portainer, mostly because CapRover does not have very good collaborative environment (eg. A single password for access)

With 20Eur a month and a VPS on Digital Ocean you can get quite far.

I also made a small project to spin up a PaaS like environment with docker swarm, Portainer and Traefik if you're interested: https://github.com/sergioisidoro/honey-swarm