-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracker to stop rebuilding FCOS #210
Comments
We naturally won't need this anymore once we stop rebuilding FCOS.
OK yup, that's the big one. I guess for that we'd need something like openshift/os#498.
coreos/fedora-coreos-tracker#767
These are Fedora packages, right? Should be able to package layer.
Same as
These are also Fedora packages, right?
We can mask the Zincati service.
If we start package layering, then we need the repos enabled. But I think we could have a new mode in rpm-ostree where we only allow some package layering. Alternatively... we ship all the Fedora packages we need in a separate container? (Something like OS extensions, but it'd need to be more closely integrated.)
I think these could all be part of the Ignition config, no? So yeah, it seems like the big ones are |
As a concrete example, if OKD doesn't rebuild FCOS, then it becomes much easier to add Prow testing of OKD to https://github.com/coreos/fedora-coreos-config, which I think would be of great benefit to OKD (and also ties into coreos/fedora-coreos-tracker#767; see coreos/fedora-coreos-tracker#767 (comment)). |
iiuc that can be done only after https://hackmd.io/@darkmuggle/rJw8Cyh9_ is accepted as an enhancement, right?
That'd require us to fork installer again and/or carry more patches for MCO |
Would be nice to not block on that if possible.
Ahh right OK, that rings a bell now (sorry, I don't have a good handle on all the backstory here). Hmm, if it can't live in the installer/MCO, it seems like those projects should at least define a way for OKD to extend them at build time for what it needs. |
Sure, but I'm not aware of any other way to create an additional layer on top of FCOS really. Previously we used
We pivot from genuine FCOS image by extracting MCO from
We have a defined way how to extend installer, but the idea is to keep changes as minimal as possible, so that we wouldn't wait for ages for lgtm and avoid filling up openshift-installer with FCOS-specific logic. |
We can also add NetworkManager to this list (https://github.com/openshift/okd-machine-os/blob/master/NM-1.32-copr.repo) until this is resolved with F35 rebase. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md is highly relevant here. |
The README includes details on the diff between FCOS and OKD. Let's figure out how to address each of them without having to rebuild FCOS.
The text was updated successfully, but these errors were encountered: