![]() EKS-Anywhere (EKS-A) (poc) - we have been working on adding CAPMVM as a provider to EKS-A.fl - an experimental CLI for interacting with flintlock to manage the lifecycle of microvms.Image Builder - this is where we build the container images that we use for root volumes and kernels for the microvm.So a microvm becomes a whole Kubernetes node. Its responsible for creating microvms on various hosts via calls to Flintlock and bootstrapping Kubernetes on those microvms. Cluster API Provider Microvm (CAPMVM) - this provides the Kubernetes cluster creation/lifecycle management (along with the Cluster API more generally).We integrate heavily with containerd as a way to use container images as the volumes for the pying rawfs files around is a real pain and very slow. It does not know of Kubernetes and could therefore be used to start a microvm to accomplish any task you choose. flintlock - this is an agent that's deployed to a host machine (physical or virtual) which enables you to start/manage microvms via API calls.While we work on this, if you notice the offical site doesn't have everything you need right now, you can head on over to our getting started repo where we have documentation, demos and some automation goodies for you □. Advanced guides to running Liquid Metal in production.Getting started tutorial for running Liquid Metal on your own machine.They are still a work-in-progress, but soon they will be a one-stop-shop for everything you could ever want to know about creating Liquid Metal platform and bare-metal workload clusters: □ BREAKING NEWS □ There are now brand new and extremely shiny user docs published right here □. We support Firecracker and experimentally Cloud Hypervisor. Hang on, what is this microvm thing you mention!?! A microvm is a very lightweight virtual machine that optimizes for speed and less resource consumption over supporting a wide array of devices/etc. Using standard kubernetes and linux kernel and operating system capabilities.Support clusters where direct access to hardware acceleration is needed (i.e.Minimizing resource footprint without sacrificing hard isolation.More clusters/nodes on the available bare-metal hosts.Create lightweight clusters to maximize the available compute.Declaratively provision Kubernetes clusters dynamically on lightweight virtual machines (i.e.Thanks for visiting, this organization contains all the projects related to Weaveworks Liquid Metal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |