flintlock
Lock, Stock, and Two Smoking MicroVMs. Create and manage the lifecycle of MicroVMs backed by containerd. (by weaveworks-liquidmetal)
homelab
By stemid-ansible
Our great sponsors
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flintlock
Posts with mentions or reviews of flintlock.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-27.
- Firecracker internals: deep dive inside the technology powering AWS Lambda(2021)
-
is kubeadm sufficient?
Thanks for the feedback. I haven't tried BYOH yet, I am using vcluster, but I've been meaning to try flintlock and Liquid Metal.
-
Bare Metal Solutions
Have a look at Liquid Metal using microvms on baremetal and using flintlock. It's pretty frigging awesome. :)
homelab
Posts with mentions or reviews of homelab.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-11.
- My homelab setup's re-usable Ansible role for Dynamic DNS from a gateway/router to AWS Route53 (in case anyone is interested)
-
On-Prem Deployments - How are you doing it?
At home in my Homelab I use PXE to provision bare metal nodes, and Ansible to deploy k8s on them. I know this setup isn't really used for anything yet, but I'm kinda proud of it. I can reprovision nodes at will by simply issuing one command, no monitor needed, no keyboard needed. That's the same level of comfort as a hypervisor, but it's bare metal.
-
What's your private cluster environment for Kubernetes-related dev
This is my new repo for my homelab and it includes a k8s.yml file, which is much cleaner and uses more Ansible roles to keep various tasks separated. So you can easily break off k8s.yml and all the k8s roles into your own repo if you want to steal it. I'm not completely done with this setup though, I'm testing FluxCD right now because I might want to ditch ArgoCD.
-
Bare Metal Solutions
I ended up writing my own, twice actually. Just re-wrote my entire k8s setup for my new homelab. It's published here on gitlab.com. It's not very well documented since it's for personal use but I think it emphasizes how easy it is to setup kubeadm and why there is little reason to make it more complicated than it needs to be.
What are some alternatives?
When comparing flintlock and homelab you can also consider the following projects:
talos - Talos Linux is a modern Linux distribution built for Kubernetes.
ansible-role-k3s - Ansible role for deploying k3s cluster
ansible-role-k3s - Ansible role for installing k3s as either a standalone server or HA cluster.
runq - run regular Docker images in KVM/Qemu
k3s - Lightweight Kubernetes
rke2
hetzner-k3s - A CLI tool to create and manage Kubernetes clusters in Hetzner Cloud using the lightweight distribution k3s by Rancher.
vHive - vHive: Open-source framework for serverless experimentation