Releases: coreos/ignition
Releases · coreos/ignition
v2.3.0
Starting with this release, ignition-validate binaries are signed with the Fedora 32 key.
Features:
- Allow specifying HTTP headers when fetching remote resources (3.1.0)
- Support compression for CA certs and merged/replaced configs (3.1.0)
- Support
sha256
verification hashes (3.1.0) - Support compression for
data
URIs - Log structured journal entry when user config is found
- Log structured journal entry when SSH keys are written
Changes:
- Unify
CaReference
,ConfigReference
,FileContents
structs intoResource
(3.1.0) - Mark the 3.1.0 config spec as stable
- No longer accept configs with version 3.1.0-experimental
- Create new 3.2.0-experimental config spec from 3.1.0
Bug Fixes:
- Fix ignition-validate for config versions other than 3.0.0
- Fix config fetch and status reporting on Packet
v2.2.1
v2.2.0
Features:
- Add Exoscale and Vultr providers
- On QEMU/s390x and QEMU/ppc64le, fetch Ignition config from a virtio block device (experimental)
Changes:
- Don't relabel
/root
and/home
Bug Fixes:
- Fix enabling systemd instantiated services
- Fail if SSH keys cannot be written
- Fix partition creation on s390x
No artifacts for this release.
v0.35.0
v2.1.1
Note: v2.1.0 was tagged, but not released, this includes notes for both. See the NEWS file for which changes are in which tag.
Bug Fixes:
- Fix panics when processes Ignition starts fail
- Do not panic when filesystem paths are unspecified
- Specify the correct config version HTTP Accept headers when fetching configs
- Write the config cache file atomically
- Relabel symlinks for masking systemd units
- Fix bug where empty GPT labels were treated as errors
- Do not generate warnings if mode is unset for files with only an append section
- Validate HTTP(S) proxy urls in spec 3.1.0-experimental
Features:
- An ignition-validate container is now built and can be used instead of
the ignition-validate binaries - Ignition now logs the name of the stage it is running
- Ignition now relabels files directly instead of writing systemd units to do so. Requires Linux 5.4.0+ or a patch. See operator notes for more details
- Add optional "fetch" stage to cache the rendered config, but not apply any of it
- Add support for aliyun cloud
- Add support for zVM hypervisor
- Add support for specifying mount options for filesystems in spec 3.1.0-experimental
Dependency Changes:
- Ignition no longer needs the chroot or id binaries in the initramfs
v0.34.0
Bug Fixes:
- Fix bug where AWS region is not set correctly for fetches from s3
- Fix bug where empty GPT labels were treated as errors
Changes:
- Ignition now logs the name of the stage it is running
Features:
- Add optional "fetch" stage to cache the rendered config, but not apply
any of it - Add support for aliyun cloud
v2.0.1
v0.33.0
v2.0.0
Bug Fixes:
- Use
/run/ignition/dev_aliases
instead of/dev_aliases
when creating our
own symlinks to devices in/dev
Test Changes:
- Rename tests to use dots.with.lowercase
Public Go API Changes:
- Replace
config/validate
api withgithub.com/coreos/vcontext
Validate()
functions in config/* now follow the vcontext validation interface
v2.0.0-beta
Features:
- Add configuration spec 3.1.0-experimental
- Allow specifying HTTP(S) proxies in spec 3.1.0-experimental
- Validate hard links do not link to directories
- Validate paths do not include links specified in the config
Bug Fixes:
- Include major version in go.mod correctly
- Fix SELinux relabeling of systemd unit files
- Update documentation for spec 3.0.0+
Changes:
- Remove all deprecated fields in configuration specs
- Remove
ec2
platform id in favor ofaws
- Remove
pxe
platform as it is not a platform - Fail if files, links, and directories conflict after symlink resolution
- Do not fail when writing directories or links if overwrite is false and a
matching directory or link already exists