Lifecycle of server image (OS)

Prev Next

Available in VPC

NAVER Cloud Platform operates with the following Life cycle policy for server image (OS) services to provide you with stable cloud services.

The operation status of Server Image is as follows:

  1. In-service
  2. Fade-out
  3. Retired

1. In-service

  • Provide and support the server image (OS) services that are available on NAVER Cloud Platform.
  • See the "update kernel" user guide for each OS to view or update the kernel information of the server images (OS).
Caution

When updating the kernel, make sure to check the "caution on updating kernel" in the guide and the order in which to perform them.

2. Fade-out

Those OS that the manufacturers have ended support fade out.

  • Due to the lack of critical services such as security patches from the manufacturer, there is a risk of exposure to hacking attacks that exploit vulnerabilities, and technical and feature updates such as vulnerability remediation are not provided, it is recommended to migrate to the latest version of the server images.

  • Previously created servers will continue to be available for use.

  • Notice to fade out

    • To ensure reliable performance and service, it is possible to fade out the older versions of the OS even if there is still time left for the vendor's EOS period to stop support.
    • We inform the schedule of fade-out in advance through the announcement/mail and console.
  • Servers created with "fade-out" server images

    • Not visible in the server creation console (new servers cannot be created)
    • Auto Scaling Group created with the "NCP server images" that has been discontinued will not proceed to scale out. Recommended to replace L/C with the latest version
    • Service operation and technical support provided

3. Retired

The server images that are faded-out and no longer available for service support.

  • The service operation and support will not provided for "retired" server images.

  • Notice to retirement

    • The retired images are selected from "fade-out" server images and change status with a 6-month notice.
  • Servers created with "retired" server images have the following restrictions:

    • Cannot "create similar server" or "create additional storage" for a server created with retired server images
    • Cannot create Launch Configuration and Auto Scaling Group with retired server images, Auto Scale out not available
    • Cannot create a server with "my server image" created with retired server images
    • Service operation and technical support not provided
Note
  • To retain data on the target server, you can take a "snapshot" and create a "storage." For more information, see the Create storage with snapshot guide.

(Note) OS Lifecycle by vendor

OS retirement schedules by vendor are as follows. See the vendor's official site for the lifecycle of each OS.

Server image (OS) End-of-service (EOS) dates by vendors EOS by OS manufacturer (official website)
NAVIX 9 May 31, 2032 https://navix.navercorp.com/about/
CentOS 7.X June 30, 2024 https://www.centos.org/cl-vs-cs/#end-of-life
Rocky Linux 8.X May 31, 2029 https://wiki.rockylinux.org/rocky/version/
Rocky Linux 9.X May 31, 2032 https://wiki.rockylinux.org/rocky/version/
Ubuntu Server 18.04 April 30, 2023 https://wiki.ubuntu.com/Releases
Ubuntu Server 20.04 April 30, 2025 https://wiki.ubuntu.com/Releases
Ubuntu Server 22.04 April 30, 2028 https://wiki.ubuntu.com/Releases
RHEL 7.X June 30, 2024 https://access.redhat.com/support/policy/updates/errata
RHEL 8.X May 31, 2029 https://access.redhat.com/support/policy/updates/errata
RHEL 9.X May 31, 2032 https://access.redhat.com/support/policy/updates/errata
Windows Server 2016 January 12, 2027 https://docs.microsoft.com/ko-kr/lifecycle/products/
Windows Server 2019 January 09, 2029 https://docs.microsoft.com/ko-kr/lifecycle/products/