| I use Kubernetes for almost everything (including my pet projects) and I see the value it brings, even if for increased complexity (although k3s is a pretty good middle ground). But none of these things you mentioned are unsolvable or require manual intervention. > What if a server gets rebooted Then the rsync/scp would fail and I would notice it in deployment logs. Or it should be straightforward to monitor current version across a fleet of baremetal. > Maybe you lost internet while doing the update True, but even Ansible recommends running a controller closer to target machines. > What about a broken build That's what tests are for. > maybe migration problem That's trickier, but unrelated to deployment method. > How do you revert (push an older tarball) By... pushing an older tarball? |