-
Notifications
You must be signed in to change notification settings - Fork 130
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
Major-changes: Document the switch to OCI for updates #698
base: main
Are you sure you want to change the base?
Conversation
With the f42 rebase we will switch disk images to use OCI for updates. While this is transparent for most users, it's still a big technical change so it's worth mentionning it, at least so users using can look into it. See https://fedoraproject.org/wiki/Changes/CoreOSOstree2OCIUpdates coreos/fedora-coreos-tracker#1823
|
||
=== Planning | ||
|
||
This change has been introduced first in bootimages for the testing stream, for the Fedora 42 rebase. After a few releases |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change has been introduced first in bootimages for the testing stream, for the Fedora 42 rebase. After a few releases | |
This change will be introduced first in new disk images for the testing stream, as part of the rebase to Fedora 42. After a few releases |
|=== | ||
|Update Stream |Targeted release date | ||
|
||
|`next` | 2025-02-04 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those dates may change so let's write the condition (first release on F42) here instead. We'll update the page once we have the exact releases.
With this change, the hosts will pull updates from the Quay.io container registry instead. | ||
This is a transparent change, except for proxied environnements, as the nodes will reach to a different address for updates. | ||
|
||
Note: Disk images will be updated first, so new installations of F42 based Fedora CoreOS will use OCI images. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: Disk images will be updated first, so new installations of F42 based Fedora CoreOS will use OCI images. | |
Note: Disk images will be updated first, so new installations of Fedora CoreOS based on Fedora 41 will use OCI images. |
|
||
Currently, Fedora CoreOS hosts pull updates from the OSTree repository. | ||
With this change, the hosts will pull updates from the Quay.io container registry instead. | ||
This is a transparent change, except for proxied environnements, as the nodes will reach to a different address for updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We claim that it's transparent and then mention exceptions. Let's say that it should be transparent but the following points may require attention: proxy configuration, etc.
After a few releases, we will migrate existing nodes. | ||
|
||
This change is only scoped to switching to OCI as the transport for Fedora CoreOS content. | ||
While derivation of these Fedora CoreOS images is possible with containers builds and use bootc, this comes with limitations: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will need some rewording
With the f42 rebase we will switch disk images to use OCI for updates. While this is transparent for most users, it's still a big technical change so it's worth mentionning it, at least so users using can look into it.
See https://fedoraproject.org/wiki/Changes/CoreOSOstree2OCIUpdates coreos/fedora-coreos-tracker#1823