Image Builder v2 tracker

Tracking epic to group steps

Following discussion here, this is how I am going to proceed.

Phase 1:

• Update the kernel image to only contain the kernel binary https://github.com/weaveworks-liquidmetal/image-builder/issues/31
• Create a new kernel-mod image containing just the kernel modules https://github.com/weaveworks-liquidmetal/image-builder/issues/31
• Update our ubuntu base image to not copy in kernel stuff https://github.com/weaveworks-liquidmetal/image-builder/pull/52
• Update flintlock to mount in kernel modules as a separate volume https://github.com/weaveworks-liquidmetal/flintlock/issues/537
• Update capmvm to pull in the correct images (capmvm, kernel, modules) as correct volumes https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/pull/254
• Update capmvm to have a nicer UX so people only need to provide an image (capmvm, kernel) version when using the default images https://github.com/weaveworks-liquidmetal/cluster-api-provider-microvm/issues/226

Phase 2:

• Update the experimental images in image-builder #55
• Look into how we can use the official CAPI base image instead of our own https://github.com/weaveworks-liquidmetal/image-builder/issues/30
• Create a new ubuntu-base image https://github.com/weaveworks-liquidmetal/image-builder/issues/30 from the official CAPI raw image OR contribute a smaller image to the k8s image-builder repo
• Remove our old ubuntu-base image
• Update the capmvm-k8s image to build FROM the new ubuntu-base image

Phase 3:

• (Stretch goal) Update our own builder things to use packer
• Write some docs about all this https://github.com/weaveworks-liquidmetal/image-builder/issues/41