On February 6, 2020, the Fedora/CoreOS community announced the official EOL date for CoreOS Container Linux as May 26, 2020.
How will this impact current virtual machine instances (VMs)?
Your current VMs that are running CoreOS Container Linux will not be affected. After the EOL date, you will still be able to start or stop your existing VMs that are using these images. However, your projects might be at risk because you will be running CoreOS images that are no longer supported and are not receiving security updates.
What is changing?
After May 26, 2020, CoreOS Container Linux will no longer be supported on Compute Engine, and you won't be able to create VMs using these images. You must migrate your CoreOS workloads and applications to an operating system or platform that is best suited for your business needs before the End of Life (EOL) date.
What do I need to do?
- Review the operating system lifecycle and support policy.
- Optional: Make copies of the CoreOS Container Linux images in your projects.
Migrate CoreOS workloads and applications to a platform that works best for your business. You can choose one of the following options:
- On Google Cloud, migrate containerized workloads and apps to one of the full-support options.
- If you are running docker containers, use Container-Optimized OS on Google Cloud.
The CoreOS/Fedora community recommends Fedora CoreOS (FCOS) as an option.
To get started with FCOS images on your own, start an instance using the
fedora-coreos-stableimage from the
fedora-coreos-cloudproject. For example, to create a test instance
gcloudcommand-line tool, run the following command:
gcloud compute instances create fedora-coreos-test-vm \ --image-project=fedora-coreos-cloud \ --image-family=fedora-coreos-stable
To get started with Fedora CoreOS on Google Cloud, see the Fedora CoreOS documentation .
If you have specific questions about CoreOS EOL, contact Google Cloud Support.