From 3f0047e853ea028ca9e01688edd80e90c1c69eb8 Mon Sep 17 00:00:00 2001 From: mes Date: Thu, 19 Dec 2024 17:24:44 +0000 Subject: [PATCH] Update README.md Updated the supported options, shifting Cloud Hypervisor as primary and Firecracker as secondary. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 097fed7c..1fc8b80c 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ > :tada: **This project was originally developed by Weaveworks but is now owned & run by the community. If you are interested in helping out please reach out.** -Flintlock is a service for creating and managing the lifecycle of microVMs on a host machine. We support [Firecracker](https://firecracker-microvm.github.io/) and [Cloud Hypervisor](https://www.cloudhypervisor.org/) (experimental). +Flintlock is a service for creating and managing the lifecycle of microVMs on a host machine. We support [Cloud Hypervisor](https://www.cloudhypervisor.org/) and limited ([Firecracker](https://firecracker-microvm.github.io/) review the release notes for specifics for firecracker. The original use case for flintlock was to create microVMs on a bare-metal host where the microVMs will be used as nodes in a virtualized Kubernetes cluster. It is an essential part of [Liquid Metal](https://www.weave.works/blog/multi-cluster-kubernetes-on-microvms-for-bare-metal) and can be orchestrated by [Cluster API Provider Microvm](https://github.com/liquidmetal-dev/cluster-api-provider-microvm).