Add ignition to CoreOS version compatibility mappings
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Feature Request
Environment
What hardware/cloud provider/hypervisor is being used to run Ignition?
Desired Feature
https://coreos.github.io/ignition/getting-started/
says
One of the most important parts of this config is the version number. This must match the version number accepted by Ignition. If the config version isn’t accepted by Ignition, Ignition will fail to run and the machine will not boot.
Idk if anything else uses ignition, but CoreOS does. In fact, I stumbled upon ignition via CoreOS.
Well, if I use version 3.5.0 on CoreOS 39, I have no idea if it will work , or if I need v3.4.0 or lower.
So, kindly provide supported CoreOS ignition version compatibility.
Other Information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked Ignition getting-started page and the CoreOS 39 context first. Done means documenting which Ignition config versions are supported by each relevant CoreOS version, with the compatibility mapping clear enough to prevent boot failures.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100