1 Introduction
Introduces upgrading from Oracle Cloud Native Environment (Oracle CNE) Release 1 to Release 2.
Important:
The upgrade from Oracle CNE Release 1 to Release 2 can be done with Oracle CNE Release 1.9. If you're using an earlier version of Oracle CNE, upgrade to Release 1.9 before you perform the upgrade to Release 2.
You must be running the latest available errata release of Oracle CNE Release 1.9, and all installed modules must be updated, before you perform the upgrade to Release 2. For information on upgrading to the latest errata release, see Oracle Cloud Native Environment: Updates and Upgrades for Release 1.9.
Upgrading requires a highly available Release 1 cluster. You can't upgrade single node clusters, or clusters with less than three control plane nodes.
Several upgrade paths are available. Some require access to the system's console to inject a Kickstart file at boot time. Other paths don't require this, and instead use the option of replacing the boot disk using the Oracle Linux Virtualization Manager or OCI User Interface. Use the following table to decide which upgrade path is most appropriate.
Table 1-1 Server Upgrade Options
| Server Type | Replaces Boot Disk | Requires System Boot Console Access |
|---|---|---|
|
Bare metal systems |
||
|
Oracle Linux Kernel-based Virtual Machine (KVM) instances |
Upgrade a Bring Your Own Cluster | |
| Oracle Linux Virtualization Manager Virtual Machines (VMs) | ||
|
OCI instances |
||
|
Oracle Private Cloud Appliance virtual instances |
||
|
Oracle Private Cloud at Customer virtual instances |
This is an in-place migration, where nodes are updated to use the Oracle CNE Release 2 OS. At the end of the migration:
-
All cluster nodes have the Oracle CNE Release 2 OS installed.
-
The Oracle CNE CLI can manage all nodes.
-
The nodes are running the latest version of Kubernetes, as stated in Oracle Cloud Native Environment: Release Notes.
-
All Release 1 modules are available as applications in the Oracle application catalog. All Release 1 Kubernetes applications are also available in the catalog.
The upgrade is performed using the Bring Your Own (BYO) provider. Before you begin, we recommend you read about the BYO provider in Oracle Cloud Native Environment: Concepts and Oracle Cloud Native Environment: Kubernetes Clusters to understand the architecture of a BYO cluster, and of Oracle CNE Release 2.