> Kubernetes has no advantages unless you're running a huge cluster. You're absolutely correct. Kubernetes has its advantages, even in a single-node setup. Wha

> Kubernetes has no advantages unless you're running a huge cluster. You're absolutely correct. Kubernetes has its advantages, even in a single-node setup. What many others are pointing out is that it also has significant disadvantages, too. > but then you want to control it remotely, right? By the way, I do talk to Docker (Swarm mode or standalone) deployments remotely, forwarding the socket via SSH. ssh -nNT -L /tmp/example.docker.sock:/run/docker.sock example.org docker -H unix:///tmp/example.docker.sock info (Needs user to have access to the socket, of course. If sudo with password-requirements is desirable, `ssh + sudo socat` is a viable alternative.) But, really, there is Ansible for this. Declare `docker_service` and get it deployed (or updated) as a part of the playbook. And ELK (with logging.driver=gelf for the containers or application-level) for logging. (BTW, what's nice about K8s is that IIRC it allows to exec into pods with just `kubectl exec`. With Swarm you need some script to discover the the right node and container ID, SSH into it and run `docker exec` there - no remote access.)