Skip to content

Commit

Permalink
chore: update readme with notice (#849)
Browse files Browse the repository at this point in the history
Signed-off-by: Richard Case <[email protected]>
  • Loading branch information
richardcase authored Jul 6, 2024
1 parent c467027 commit 8fcd8d3
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 3 deletions.
4 changes: 2 additions & 2 deletions COPYRIGHT.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
Copyright 2021 Weaveworks, Inc. All Rights Reserved.
SPDX-License-Identifier: MPL-2.0
Copyright 2024 The Liquid Metal Authors. All Rights Reserved.
SPDX-License-Identifier: MPL-2.0
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@

## What is flintlock?

> :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).

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/weaveworks-liquidmetal/cluster-api-provider-microvm).
Expand Down
2 changes: 1 addition & 1 deletion hack/boilerplate.generatego.txt
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
/*
Copyright The Flintlock authors
Copyright The Liquid Metal Authors

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
Expand Down

0 comments on commit 8fcd8d3

Please sign in to comment.