Skip to content

Commit

Permalink
Update README.md (#990)
Browse files Browse the repository at this point in the history
Updated the supported options, shifting Cloud Hypervisor as primary and Firecracker as secondary.
  • Loading branch information
mestadler authored Dec 26, 2024
1 parent 19f9906 commit edc2a7c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down

0 comments on commit edc2a7c

Please sign in to comment.