distribution end date , which was replaced by the project (after CoreOS project, Red Hat has combined 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's lifecycle will end. On September 1, CoreOS related resources will be removed or made read-only. For example, installation images offered for download, assemblies for cloud environments, and repositories with updates will be removed. GitHub repositories and the bug tracker will remain read-only.
From the CoreOS Container Linux distribution, the Fedora CoreOS project borrowed its bootstrapping configuration tool (Ignition), the atomic update mechanism, and the overall product philosophy. Packet technology, support for OCI (Open Container Initiative) specifications, and additional container isolation mechanisms based on SELinux have been transferred from Atomic Host. For orchestration of containers on top of Fedora CoreOS, in the future it is planned to provide integration with Kubernetes (including based on OKD).
To simplify the migration from CoreOS Container Linux to Fedora CoreOS prepared highlighting the main differences. In its current form, Fedora CoreOS cannot completely replace CoreOS Container Linux, for example, because it does not include the rkt container management tool, the Azure, DigitalOcean, GCE, Vagrant and Container Linux platforms are not supported, and regression changes and compatibility issues are not ruled out. .
For those who do not have the ability or desire to switch to Fedora CoreOS, you can pay attention to the fork , compatible with CoreOS Container Linux. fork was by Kinvolk in 2018 after Red Hat announced its intention to integrate CoreOS technologies with its products. The project was created to ensure the continued existence of CoreOS Container Linux, in the event of major changes or curtailment of development.
Flatcar Container Linux has been moved to its own independent development, maintenance, build and release infrastructure, but the state of the codebase has been synchronized with
CoreOS (changes were reduced to the replacement of branding elements). At the same time, the project developed with an eye to the possibility at any time to continue a separate existence in the event of the disappearance of CoreOS Container Linux. For example, in a separate thread "Β» for Flatcar Container Linux, experiments were conducted with the addition of new features and the application of patches.
Source: opennet.ru