Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrade OpenShift

CN2 supports EUS-to-EUS upgrades. When you upgrade OpenShift, ensure you're upgrading to an OpenShift EUS release that is supported by a CN2 release. For the list of supported releases, see https://www.juniper.net/documentation/us/en/software/cn-cloud-native/cn2-tested-integrations/cn-cloud-native-tested-integrations/concept/cn-cloud-native-tested-integrations.html.

In the simplest upgrade scenario, you’re happy with the CN2 release that you’re running and that CN2 release is compatible with the OpenShift release you want to upgrade to. In this case, just follow standard OpenShift upgrade procedures.

More likely, however, you’ll want to upgrade both OpenShift and CN2. We recommend you always upgrade CN2 to the latest release that is supported for your OpenShift release. This way, you'll get the latest features, bug fixes, and security updates for your CN2 deployment.

When you’re upgrading both OpenShift and CN2, you need to plan your upgrade path. Your upgrade path is influenced by the following:

  • OpenShift requires you to upgrade EUS releases sequentially.

    For example, to upgrade from eus-4.8 to eus-4.12, you'll need to upgrade first from eus-4.8 to eus-4.10 and then from eus-4.10 to eus-4.12.

  • The CN2 release that your cluster is currently running must be compatible with the OpenShift release you want to upgrade to.

    In the above example, before you can upgrade from eus-4.8 to eus-4.10, your cluster must run a CN2 release that is compatible with both eus-4.8 and eus-4.10. Similarly, before you can upgrade from eus-4.10 to eus-4.12, your cluster must run a CN2 release that is compatible with both eus-4.10 and eus-4.12.

  • When the above conditions are satisfied, upgrade OpenShift before you upgrade CN2.

Example 1

You want to upgrade from eus-4.8 / cn2-22.1 to eus-4.12 / cn2-23.1. One possible upgrade path is as follows:

  1. Upgrade from eus-4.8 / cn2-22.1 to eus-4.8 / cn2-22.4. You cannot upgrade to eus-4.10 yet. Your cluster must run a CN2 release that is compatible with eus-4.10 before you can upgrade to eus-4.10.

  2. Upgrade from eus-4.8 / cn2-22.4 to eus-4.10 / cn2-22.4. Now you can upgrade to eus-4.10 because your cluster is running cn2-22.4, which is compatible with eus-4.10.

  3. Upgrade from eus-4.10 / cn2-22.4 to eus-4.12 / cn2-22.4. Upgrade OpenShift to the destination release.

  4. Upgrade from eus-4.12 / cn2-22.4 to eus-4.12 / cn2-23.1. Upgrade CN2 to the destination release.

Example 2

You want to upgrade from eus-4.8 / cn2-22.3 to eus-4.12 / cn2-23.1. One possible upgrade path is as follows:

  1. Upgrade from eus-4.8 / cn2-22.3 to eus-4.10 / cn2-22.3. Since cn2-22.3 is compatible with eus-4.10, you can upgrade OpenShift to eus-4.10 straightaway.

  2. Upgrade from eus-4.10 / cn2-22.3 to eus-4.10 / cn2-22.4. Since you want to upgrade to eus-4.12 next, your cluster must run a CN2 release (cn2-22.4) that is compatible with eus-4.12.

  3. Upgrade from eus-4.10 / cn2-22.4 to eus-4.12 / cn2-22.4. Upgrade OpenShift to the destination release.

  4. Upgrade from eus-4.12 / cn2-22.4 to eus-4.12 / cn2-23.1. Upgrade CN2 to the destination release.

For information on how to upgrade OpenShift, see Red Hat OpenShift documentation (https://docs.openshift.com/container-platform/4.12/updating/preparing-eus-eus-upgrade.html) for your release.

For information on how to upgrade CN2, see Upgrade CN2.