This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Releases: weaveworks/ignite
Releases · weaveworks/ignite
v0.4.0-rc.1
v0.4.0-rc.1
The first release candidate for Ignite's biggest release yet!
There are many significant changes compared to before:
New Features
- Make base and kernel OCI images composable for a VM. You can now choose what kernel to combine with what base image freely #105
- Add the GitOps mode for Ignite using
ignite gitops
#100 - Make it possible to run
ignite create
andignite run
declaratively 5733364 - Added Prometheus metrics for
ignite-spawn
94abc52 - Implemented CNI support a889753
API Machinery
- Added the
ignite.weave.works/v1alpha1
API group with the Ignite API types ca1edc8 - Add a meta API package containing supporting but generic API types for Ignite 09d51ab
- Create composable interfaces for the internal API machinery:
Client
->Cache
->Storage
->RawStorage
->Serializer
#93 #96 #99
New Commands
Documentation
- Add user-facing documentation and guides #113
- Generate OpenAPI specifications f1c5bfd
- Add API type documentation 218c947
- Added architecture diagram da53f9f
- Added graph of module dependencies be7cc08
Internal Improvements
v0.3.0
Major release with significant UX and internal improvements:
- There is no longer a difference between an Ignite image and an OCI image, this is now the same thing.
- Ignite operates on OCI images directly, for both OS images and kernels. The kernel is expected to be coupled with the image given to
ignite run
, in/boot/vmlinux
.
- Ignite operates on OCI images directly, for both OS images and kernels. The kernel is expected to be coupled with the image given to
- It is now possible to do
ignite run [OCI image]
directly, and everything (e.g. pulling the image) is handled automatically. e.g.ignite run -i weaveworks/ignite-ubuntu
. - Now
ignite images
shows OCI images that are cached and ready to use, andignite kernels
the kernels already imported from base images. - Added an example usage guide for running a Kubernetes cluster in HA mode using kubeadm and Ignite.
- Removed
ignite build
, andignite image/kernel import
; as these are no longer needed - Importing an image from a tar file is no longer possible, package the contents in an OCI image instead
- Added a new command
ignite ssh [vm]
and flag:ignite run --ssh
. This allows for automatic SSH logins. - Now Ignite logs user-friendly messages by default. To get machine-readable output, use the
--quiet
flag. - Ignite now requires the user to be
root
. This will be revisited later, when the architecture has changed. - The command outputs and structure is now more user-friendly.
- Fixed several bugs both under the hood, and user-affecting ones
v0.2.0
Major release with significant improvements
- Ignite is now using
devicemapper
under the hood, for overlay snapshots for filesystem writes, allowing for image reuse, efficient use of space and way faster builds! - Added sample Ubuntu 18.04 and CentOS 7 OS images & a 4.19 kernel build
- Automatic network configuration, now the OS image doesn't need to enable DHCP, as that is done in the kernel
- Automatically populate
/etc/hosts
and/etc/resolv.conf
, too - Add an option to bind a port exposed by the VM to a host port (
ignite run -p 80:80
) - Add an option for modifying the kernel command line (
ignite run --kernel-args
) - Add an option to copy files from the host into the VM (
ignite run --copy-files
) - Add an option to specify the amount of cores, RAM, and overlay size (
ignite run --cpus 2 --memory 1024 --size 4GB
) - Removed the need for the Ignite container to run with
--privileged
- Allow for force-deletions of images, kernels and vms.
- Added documentation.
- Moved repo from luxas/ignite to weaveworks/ignite
Use it
Download the attached binary, add it to $PATH
, and execute the following commands:
$ ignite build weaveworks/ignite-ubuntu:v0.2.0 \
--name ubuntu-image \
--import-kernel ubuntu-kernel
$ ignite images
$ ignite kernels
$ ignite run ubuntu-image ubuntu-kernel --name my-vm
$ ignite ps
$ ignite logs my-vm
$ ignite attach my-vm
# Cleanup
$ ignite stop my-vm
$ ignite rm my-vm
$ ignite rmi ubuntu-image
$ ignite rmk ubuntu-kernel
Also make note of the known limitations