> Most managed Kubernetes systems cannot even provision in that time frame.
when was the last time you used k8s?! I mean as of now there is even the expirmental k3os which boots a fully fledged k8s in seconds. you can even built a cluster with it. sadly HA backplane is still not available since k3s is still early in its development.
I'm talking here about the managed Kubernetes offerings from AWS and Azure. As for when I last used them: waiting for provisioning right now (18 mins and counting) is affording me the time to comment on this article.
maybe you should use gcloud gke. or even digitalocean, they provision in under then minutes aswell.
not sure why aws and azure take so long.
I work on provisioning tools, I use all of them. I've definitely seen GKE take just as long as the others...
How long did it take you to install Triton?
How many systems did you need to install Triton?
How much memory did(do) the individual systems running Triton have?
Which documentation did you follow to install Triton?
The total time to install across 4 hosts was probably 15 mins or so. There used to be a post on the Joyent blog that explained the setup for small scale, I'm not sure if it is still there.
Actually I'd say the Triton install is not only trivial, but should be a model for other similar systems. During my testing with Intel NUCs, I had a usable system deploying containers in under 20 minutes. Most managed Kubernetes systems cannot even provision in that time frame.
> you just can't run SmartOS on the cloud.
The installer may lead you to the USB and install path, but it is not necessary. I built Vagrant boxes that had SmartOS on a regular disk, and I believe that more recently SmartOS has been running well in GCP. There is no reason it could not run in AWS or Azure, either.