So, now that the Kubernetes based rack has launched, and the documentation is live
It contains no mention of AWS Fargate anymore. Has support for AWS Fargate been dropped? Is it something that has just not yet been added back in since the priority was on the multi-cloud features not the more advanced features of individual clouds?
While abstracting away complexity is why I use Convox in the first place, the new documentation seems to go out of its way to avoid mentioning what underlying mechanisms power things, like the primitives section… making it harder to reason about what is going to happen in a production environment by leveraging the extant body of knowledge available online with regards to how Kubernetes operates in practice. I cant even tell from the documentation if Convox deploys a Kubernetes environment on AWS using the managed Kubernetes service (AKE) or if Convox builds the entire Kubernetes environment. Is my Database going to be some ephemeral container or on RDS?
The documentation mentions pods only in in the log output of other commands. A pod is one of Kubernetes most basic primitives, at some point in the future are we going to get a mechanism for saying that a service is composed of multiple containers/processes deployed together as a single pod? Sidecars like this are a significant tool used by a lot of things in the Kubernetes ecosystem, so lacking support for them is a significant limitation.