Why not Kubails?

You probably shouldn't use Kubails.

As much as I'd love for everyone to be using Kubails, it is far more realistic for me to say that you probably shouldn't be using Kubails.

Here's why.

And if you haven't already, I suggest going through the Introduction and the FAQ to learn more about what Kubails is.

It's a one man project

Hi! It's me! The one person creating/maintaining Kubails.

This has its implications. One person only has so much time for maintenance, support, etc.

As such, if you think you'll need support outside of what the documentation offers (and outside what could be answered through some GitHub issues), then I suggest you use a managed PaaS.

It's still pretty alpha

As much as I've been using Kubails for several projects — some of which have been going for a while now — that doesn't mean I have the utmost confidence to say that anyone else should use it. If only because it's never been tested under a true production load.

Kubails really was designed to fit my personal needs for bootstrapping projects, so I don't think it's a point where I'm confident enough to say that "yes, this'll fit your needs too".

You don't want to use Docker/Kubernetes/GCP/etc

Obviously, if you don't want to use/learn the underlying technologies, there's no point in you using Kubails.

You want to use AWS

As I outlined in the FAQ, AWS support is not currently in the works. As such, you must assume that it'll never happen.

So yeah... don't use Kubails if you must use AWS.