end date for the distribution support , which has been replaced by the project (after of the CoreOS project, Red Hat unified Fedora Atomic Host and CoreOS Container Linux into a single product). The last update for CoreOS Container Linux is scheduled for May 26, after which the project lifecycle will conclude. On September 1, resources related to CoreOS will be removed or switched to read-only mode. For instance, the downloadable installer images, cloud environment builds, and update repositories will be deleted. The repositories on GitHub and the bug tracking system will remain available in read-only mode.
From the CoreOS Container Linux distribution, the Fedora CoreOS project borrowed the configuration tooling during the initial boot stage (Ignition), atomic update mechanisms, and the overall product philosophy. The package management technology, support for OCI (Open Container Initiative) specifications, and additional container isolation mechanisms based on SELinux were transferred from Atomic Host. Future plans include integration with Kubernetes (including on the basis of OKD) for container orchestration on top of Fedora CoreOS.
To simplify the migration from CoreOS Container Linux to Fedora CoreOS, a , outlining the main differences, has been prepared. In its current form, Fedora CoreOS cannot completely replace CoreOS Container Linux, for example, as it does not include the rkt container management toolkit, does not support Azure, DigitalOcean, GCE, Vagrant, and Container Linux platforms, and there is also the possibility of regressions and compatibility issues.
For those who cannot or do not wish to switch to Fedora CoreOS, they may consider the fork , compatible with CoreOS Container Linux. The fork was by Kinvolk in 2018 after Red Hat announced intentions to integrate CoreOS technologies with its products. The project was created to ensure the continued existence of CoreOS Container Linux in case of significant changes or halting of development.
Flatcar Container Linux has been migrated to its own independent infrastructure for development, maintenance, building, and releasing updates, but the state of the codebase has been synchronized with
CoreOS (the changes were focused on rebranding elements). Meanwhile, the project evolved with the prospect of continuing independent existence in case CoreOS Container Linux disappeared. For instance, in a separate branch of "" experiments were conducted for Flatcar Container Linux regarding the addition of new features and the application of patches.
Source: opennet.ru
