Maybe You Don't Need Kubernetes
Over the years, I've deployed applications using various combinations of custom RPMs, Chef, Heroku, Docker, ECS and Kubernetes.<p>If you can, you should probably deploy to Heroku. (Or a similar service.) It's far cheaper than spending time on devops. Just run "git push" and you're running.<p>When I've deployed on ECS (or other "simple" orchestrators), I've found that I ultimately wound up re-inventing lots of Kubernetes features.<p>So if you can't use Heroku, but you <i>do</i> know basic Docker, then it's worth considering somebody's fully-managed Kubernetes. Google's is nice. Amazon's is a considerably more work. I hear Microsoft's is still a bit sketchy. And I'd love to take a look at Digital Ocean's. But do <i>not</i> attempt to host your own Kubernetes if you can possibly avoid it.<p>If you do try Kubernetes, then read a book like <i>Kubernetes: Up & Running</i> first. Kubernetes is not self-explanatory, but it's pretty straightforward if you're willing to spend a few days reading.<p>Finally, don't overcomplicate it. Just use the basic stuff for as long as you can before trying to layer all sorts of other tools over it.