> k8s instead of Google App Engine or other managed PaaS
K8s is also available as a managed solution with GKE Autopilot, which in general is a breeze to use.
> You never worry about the problems listed in this article.
You still have to. If you look at the whole list of "how-to" guides one of the language docs for GAE (e.g. [0]), you see that there are about as much topics to worry about than if you were deploying to K8s. They also pretty much 1:1 map to things in K8s, but in contrast are non-standardized across vendors.
> deploying it with minimal config
I think the article laid out quite well how for a minimal deployment, the configuration you need for K8s is also pretty minimal. Yes, it might be more than a one-liner for a GAE config, but most of it is boilerplate you can ignore.
K8s is also available as a managed solution with GKE Autopilot, which in general is a breeze to use.
> You never worry about the problems listed in this article.
You still have to. If you look at the whole list of "how-to" guides one of the language docs for GAE (e.g. [0]), you see that there are about as much topics to worry about than if you were deploying to K8s. They also pretty much 1:1 map to things in K8s, but in contrast are non-standardized across vendors.
> deploying it with minimal config
I think the article laid out quite well how for a minimal deployment, the configuration you need for K8s is also pretty minimal. Yes, it might be more than a one-liner for a GAE config, but most of it is boilerplate you can ignore.
[0]: https://cloud.google.com/appengine/docs/legacy/standard/go11...