Media & Entertainment
At their 2018 annual Re:Invent conference, AWS announced an exciting new product called “Firecracker” that is quickly setting the cloud-native ecosystem on fire. Firecracker is a Virtual Machine Manager (VMM) exclusively designed for running transient and short-lived processes. In other words, it is optimized for running functions and serverless workloads that require faster cold start and higher density.
Using the same technology that Amazon uses for AWS Lambda and AWS Fargate, Firecracker delivers the speed of containers with the security of VMs and has the potential to disrupt the current container and serverless technologies.
While Firecracker has a ton of potential, it’s still in its early stages so getting it up and running can be a bit tedious. The goal of Ignite is to solve this issue by adopting its developer experience from containers.
With Ignite, you just pick a container image that you want to run as a VM and then execute
ignite run instead of
There’s no need to use VM-specific tools to build
.qcow2 images, just do a
docker build from any base image you want (e.g.
ubuntu:18.04 from Docker Hub), and add your preferred content.
You can even use Buildpacks! As seen in my other blog post here. In this case, you would just follow the same steps, except you would build the image via the
Firekube is a new open-source Kubernetes distribution that enables the use of Weave Ignite and GitOps to enable the setup of secure VM clusters. Firekube pulls everything from Git, detects your operating system and can boot up a secure cluster of VMs from nothing in 2.5 minutes.
A Firekube cluster has the following properties:
Prerequisites: Docker, Git, kubectl 1.14+.
cdinto it. Use the
SSHgit URL as the script will push an initial commit to your fork:
export user="" # Your GitHub handle or org git clone firstname.lastname@example.org:$user/wks-quickstart-firekube.git cd wks-quickstart-firekube
This step will take several minutes.
KUBECONFIG environment variable as indicated at the end of the installation:
Enjoy your Kubernetes cluster!
$ kubectl get nodes NAME STATUS ROLES AGE VERSION 67bb6c4812b19ce4 Ready master 3m42s v1.14.1 a5cf619fa058882d Ready <none> 75s v1.14.1
Now that we have a cluster installed, we can commit Kubernetes objects to the git repository and have them appear in the cluster. Let’s add podinfo, an example Go microservice, to the cluster.
kubectl apply --dry-run -k github.com/stefanprodan/podinfo//kustomize -o yaml > podinfo.yaml git add podinfo.yaml git commit -a -m 'Add podinfo Deployment' git push
A few seconds later, you should witness the apparition of a podinfo pod in the cluster:
$ kubectl get pods NAME READY STATUS RESTARTS AGE podinfo-677768c755-z76xk 1/1 Running 0 30s
podinfo web UI:
kubectl port-forward deploy/podinfo 9898:9898
To use a private git repository instead of a fork of
masterbranch there. Use the SSH git URL when cloning the private repository:
git clone email@example.com:$user/$repository.git cd $repository git remote add quickstart firstname.lastname@example.org:weaveworks/wks-quickstart-firekube.git git fetch quickstart git merge quickstart/master git push
ssh-keygen -t rsa -b 4096 -C "email@example.com" -f deploy-firekube -N ""
./setup.sh --git-deploy-key ./deploy-firekube
You’ve now learned the basic steps it requires to provision a Kubernetes cluster based on Firecracker VM’s with Firekube. You should explore a bit of the different options the platform provides such as using Ignite to spin up MicroVM’s with Buildpack instead of Docker. I hope you liked this post, and I plan to dive into this a bit more in the future. Thanks for reading!