Decide: Cloud-init and ignition support #142
Labels
No labels
Area
Anaconda
Area
CI
Area
composefs
Area
dnf
Area
podman
Bug
Documentation
DO NOT MERGE
Duplicate
Enhancement
Flaky
Good first issue
Help wanted
Invalid
level-1
level-2
level-3
Meeting
Question
TEST ONLY
Version
Fedora 41
Version
Fedora 42
Version
Fedora 43
Version
Fedora 44
Version
Fedora 45
Won't fix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
atomic/tracker#142
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Create an ADR
Discuss/define cloud-init and ignition supportto Decide: Cloud-init and ignition supportTL;DR: Proposal was to build/run CI against an image as soon as possible. Need to decide how people boot the image the first time. Needs a spike OR needs a decision.
Ecosystem of choices?
TODO: Let's make some proposal ADRs. This is a longer discussion.
I would prefer that either we choose 1 or build 2. If you think about it Fedora's already offers both the Cloud edition ships with cloud-init and CoreOS with ignition.
ADR repo has been created: https://forge.fedoraproject.org/atomic/adr
Decision in progress in atomic/adr#2