7 ms·
Wouldn't it have cost less to enhance the Nomad scheduler rather than move to, and enhance, Kubernetes? This aside, Fly is in a position to build its own alter
by Dowwie 3y ago
Wouldn't it have cost less to enhance the Nomad scheduler rather than move to, and enhance, Kubernetes?
This aside, Fly is in a position to build its own alternative to K8s and Nomad from scratch, so maybe it will?
- imjonse 3y agoThey have for their infrastructure, as I understood from this and previous blogs. This is for their user-facing offering. It makes sense if people are using other cloud K8S solutions and want to migrate without rethinking too much of their existing architecture.
- tptacek 3y agoWe absolutely have not moved to K8s. We've just added a feature that lets you run K8s, in a particularly simple configuration, if K8s is what you want. If you weren't already interested in using K8s, you shouldn't touch FKS. The ordinary way someone would boot up an app on Fly.io is to visit a directory in their filesystem with a Rails or Django or Express app or something, or a Dockerfile, and just type `flyctl launch`. No K8s will be involved in any way. You have to go out of your way to get K8s on Fly.io. :)