Fly.io offers a managed Kubernetes service – but it doesn't use nodes? How does that even work? Where do the pods go?? In this video I explain how we make use of virtual kubelet to manage your cluster AND the nifty way we schedule your pods.

Fly.io offers insights into edge computing, serverless architecture, and global content delivery network (CDN), providing documentation, tutorials, and best practices for deploying and scaling applications at the network edge. By exploring Fly.io's curated content, developers can learn about Fly's edge computing platform, distributed application runtime, and HTTP/2 load balancing for building fast, secure, and scalable web applications. Whether you're optimizing latency for global users, offloading compute-intensive tasks, or deploying microservices, Fly.io offers resources to supercharge your application performance and reliability.

Fly.io

Fly Kubernetes allows for a node-less Kubernetes setup using a combination of a trimmed-down Kubernetes version called k3s for the control plane and Virtual kuet, which emulates traditional kubelet behavior. Instead of worker nodes, Fly uses virtual nodes and its own machines API to manage pods and orchestration. This decentralized approach offloads scheduling decisions to Fly’s own orchestrator, leveraging high availability and self-managed physical machines.

Kubernetes without nodes

<p>There are no workers nodes but pricing is still high just for the control plane 😞</p>
