1. Updates and Upgrades for Release 1.9
  2. Upgrading to Release 1.9

4 Upgrading to Release 1.9

This section describes how to upgrade Oracle Cloud Native Environment from Release 1.8 to Release 1.9.

When the Oracle Cloud Native Environment packages and the Kubernetes cluster are upgraded to Release 1.9, you can use the new features in this release.

Perform each step in this chapter to upgrade an environment from Release 1.8 to Release 1.9.

Important:

Before you upgrade to Release 1.9, update to the latest errata release of Oracle Cloud Native Environment Release 1.8. For information on updating the environment, see Updates and Upgrades for Release 1.8.

Changing the Software Packages Source

This section contains information on setting the location for the software packages for the OS on which you want to upgrade the Oracle Cloud Native Environment software.

Oracle Linux 9

If the OS on the nodes is Oracle Linux 9, update the package source using the information in this section.

If you're using the Oracle Linux yum server for system updates, on each node update the oracle-olcne-release-el9 release package. Enable the ol9_olcne19 repository and disable the ol9_olcne18 and ol9_olcne17 repositories, which are for the previous releases.

On each node, run: 

sudo dnf update oracle-olcne-release-el9
sudo dnf config-manager --enable ol9_olcne19
sudo dnf config-manager --disable ol9_olcne18 ol9_olcne17

If the systems are registered to use ULN, use the ULN web interface to subscribe each system to the ol9_x86_64_olcne19 channel. Ensure you unsubscribe each system from the ol9_x86_64_olcne18 andol9_x86_64_olcne17 channels, which are for the previous releases.

Oracle Linux 8

If the OS on the nodes is Oracle Linux 8, update the package source using the information in this section.

If you're using the Oracle Linux yum server for system updates, on each node update the oracle-olcne-release-el8 release package. Enable the ol8_olcne19 repository and disable the repositories for the previous releases. Disable the following repositories:

  • ol8_olcne18

  • ol8_olcne17

  • ol8_olcne16

  • ol8_olcne15

  • ol8_olcne14

  • ol8_olcne13

  • ol8_olcne12

On each node, run: 

sudo dnf update oracle-olcne-release-el8
sudo dnf config-manager --enable ol8_olcne19
sudo dnf config-manager --disable ol8_olcne18 ol8_olcne17 ol8_olcne16 ol8_olcne15 ol8_olcne14 ol8_olcne13 ol8_olcne12

If the systems are registered to use ULN, use the ULN web interface to subscribe each system to the ol8_x86_64_olcne19 channel. Ensure you unsubscribe each system from the following channels:

  • ol8_x86_64_olcne18

  • ol8_x86_64_olcne17

  • ol8_x86_64_olcne16

  • ol8_x86_64_olcne15

  • ol8_x86_64_olcne14

  • ol8_x86_64_olcne13

  • ol8_x86_64_olcne12

Upgrading the Operator Node

Upgrade the operator node with the new Oracle Cloud Native Environment software packages.

To upgrade the operator node on Oracle Linux:

  1. On the operator node, stop the olcne-api-server service: 

    sudo systemctl stop olcne-api-server.service

  2. Update the Platform CLI, Platform API Server, and utilities packages: 

    sudo dnf update olcnectl olcne-api-server olcne-utils

  3. Start the olcne-api-server service: 

    sudo systemctl start olcne-api-server.service

Upgrading the Kubernetes Nodes

Upgrade the Kubernetes nodes with the new Oracle Cloud Native Environment software packages.

On the operator node, use the olcnectl environment update command to upgrade the Platform Agent on each node in the environment. This example upgrades the Platform Agent on all nodes in the myenvironment environment. 

olcnectl environment update olcne \
--environment-name myenvironment

The Platform Agent is upgraded and the service is restarted on each node.

Upgrading the Kubernetes Cluster

Upgrade the cluster to Kubernetes Release 1.29.3.

On the operator node, use the olcnectl module update command to upgrade to the latest Kubernetes release available for Oracle Cloud Native Environment Release 1.9. This example upgrades a Kubernetes module named mycluster in the myenvironment environment to Kubernetes Release 1.29.3. 

olcnectl module update \
--environment-name myenvironment \
--name mycluster \
--kube-version 1.29.3

The --kube-version option specifies the release to which you want to upgrade. This example uses release number 1.29.3.

Important:

Ensure you upgrade to the latest Kubernetes release. To get the version number of the latest Kubernetes release for Oracle Cloud Native Environment Release 1.9, see Release Notes.

You can optionally use the --log-level option to set the level of logging displayed in the command output. By default, error messages are displayed. For example, you can set the logging level to show all messages when you include: 

--log-level debug

The log messages are also saved as an operation log. You can view operation logs as commands are running, or when they've completed. For more information using operation logs, see Platform Command-Line Interface.

When each node in the cluster is upgraded to the latest Kubernetes release, the cluster's health is validated and the upgrade completes.

Upgrading the Calico Module

If you have the Calico module installed, you must upgrade it.

Important:

Ensure you upgrade to the latest releases for each component in this section. To get the version numbers of the latest releases for Oracle Cloud Native Environment Release 1.9, see Release Notes.

To upgrade Calico, on the operator node, use the olcnectl module update command to upgrade to the latest Calico release available for Oracle Cloud Native Environment Release 1.9. This example upgrades an Calico module named mycalico in the myenvironment environment to Calico Release 3.27.0. 

olcnectl module update \
--environment-name myenvironment \
--name mycalico \
--calico-version 3.27.0

The --calico-version option specifies the release to which you want to upgrade. This example uses release number 3.27.0.

Important:

Ensure you upgrade to the latest Calico release. To get the version number of the latest Calico release for Oracle Cloud Native Environment Release 1.9, see Release Notes.

You can optionally use the --log-level option to set the level of logging displayed in the command output. By default, error messages are displayed. For example, you can set the logging level to show all messages when you include: 

--log-level debug

The log messages are also saved as an operation log. You can view operation logs as commands are running, or when they've completed. For more information using operation logs, see Platform Command-Line Interface.

Upgrading the Oracle Cloud Infrastructure Cloud Controller Manager Module

If you have the Oracle Cloud Infrastructure Cloud Controller Manager module installed, you must also upgrade it.

To upgrade the Oracle Cloud Infrastructure Cloud Controller Manager module, on the operator node, use the olcnectl module update command. This example upgrades the module named myoci in the myenvironment environment to the Oracle Cloud Infrastructure Cloud Controller Manager module Release 1.28.0

olcnectl module update \
--environment-name myenvironment \
--name myoci \
--oci-ccm-version 1.28.0 \
--oci-container-registry "" \
--ccm-container-registry ""
The --oci-ccm-version option specifies the release to which you want to upgrade. This example uses release number 1.28.0.

Important:

Ensure you upgrade to the latest release of the Oracle Cloud Infrastructure Cloud Controller Manager module. To get the version numbers of the latest releases for Oracle Cloud Native Environment Release 1.9, see Release Notes.

For registry options --oci-container-registry and --ccm-container-registry, the example assumes public registries are being used, and both options are therefore set to an empty string ("") so the Platform API Server automatically configures the correct public container registry from which to pull the Oracle Cloud Infrastructure Cloud Controller Manager container images. If, however, you're using private registries, and have already set values for --oci-container-registry and --ccm-container-registry during the installation process, then you don't have to specify these options.

You can optionally use the --log-level option to set the level of logging displayed in the command output. By default, error messages are displayed. For example, you can set the logging level to show all messages when you include: 

--log-level debug

The log messages are also saved as an operation log. You can view operation logs as commands are running, or when they've completed. For more information using operation logs, see Platform Command-Line Interface.

Upgrading the Istio Module

If you have the Istio module installed, you must also upgrade it.

Important:

Ensure you upgrade to the latest releases for each component in this section. To get the version numbers of the latest releases for Oracle Cloud Native Environment Release 1.9, see Release Notes.

To upgrade Istio, on the operator node, use the olcnectl module update command to upgrade to the latest Istio release available for Oracle Cloud Native Environment Release 1.9. This example upgrades an Istio module named myistio in the myenvironment environment to Istio Release 1.20.4. 

olcnectl module update \
--environment-name myenvironment \
--name myistio \
--istio-version 1.20.4

The --istio-version option specifies the release to which you want to upgrade. This example uses release number 1.20.4.

When you upgrade to Istio Release 1.20.4, the update iterates through each Istio release up to Release 1.20.4. When each node in the cluster is upgraded to the next Istio release, the cluster's health is validated. If the cluster is healthy, the cycle of back up, upgrade to the next release, and cluster validation starts again, until all nodes are upgraded to the latest Istio release.

You can optionally use the --log-level option to set the level of logging displayed in the command output. By default, error messages are displayed. For example, you can set the logging level to show all messages when you include: 

--log-level debug

The log messages are also saved as an operation log. You can view operation logs as commands are running, or when they've completed. For more information using operation logs, see Platform Command-Line Interface.

Upgrading the KubeVirt Module

If you have the KubeVirt module installed, you must also upgrade it.

To upgrade the KubeVirt module, on the operator node, use the olcnectl module update command. This example upgrades the module named mykubevirt in the myenvironment environment to the KubeVirt module Release 1.1.1

olcnectl module update \
--environment-name myenvironment \
--name mykubevirt \
--kubevirt-version 1.1.1

The --kubevirt-version option specifies the release to which you want to upgrade. This example uses release number 1.1.1.

Important:

Ensure you upgrade to the latest release of the KubeVirt module. To get the version numbers of the latest releases for Oracle Cloud Native Environment Release 1.9, see Release Notes.

You can optionally use the --log-level option to set the level of logging displayed in the command output. By default, error messages are displayed. For example, you can set the logging level to show all messages when you include: 

--log-level debug

The log messages are also saved as an operation log. You can view operation logs as commands are running, or when they've completed. For more information using operation logs, see Platform Command-Line Interface.