28 Management Cluster #
This section covers how to perform the various Day 2
operations related to upgrading your management
cluster from one Edge platform version to another.
The Day 2
operations are automated by the Upgrade Controller (Chapter 21, Upgrade Controller) and include:
SL Micro (Chapter 8, SLE Micro) OS upgrade
RKE2 (Chapter 15, RKE2)/K3s (Chapter 14, K3s) upgrade
SUSE additional components (Rancher, Neuvector, etc.) upgrade
28.1 Prerequisites #
Before upgrading your management
cluster, the following prerequisites must be met:
SCC registered nodes
- ensure your cluster nodes' OS are registered with a subscription key that supports the OS version specified in the Edge release (Section 37.1, “Abstract”) you intend to upgrade to.Upgrade Controller
- make sure that theUpgrade Controller
has been deployed on yourmanagement
cluster. For installation steps, refer to Installing the Upgrade Controller (Section 21.2, “Installing the Upgrade Controller”).
28.2 Upgrade #
Determine the Edge release (Section 37.1, “Abstract”) version that you wish to upgrade your
management
cluster to.In the
management
cluster, deploy anUpgradePlan
that specifies the desiredrelease version
. TheUpgradePlan
must be deployed in the namespace of theUpgrade Controller
.kubectl apply -n <upgrade_controller_namespace> -f - <<EOF apiVersion: lifecycle.suse.com/v1alpha1 kind: UpgradePlan metadata: name: upgrade-plan-mgmt-3-1-X spec: # Version retrieved from release notes releaseVersion: 3.1.X EOF
NoteThere may be use-cases where you would want to make additional configurations over the
UpgradePlan
. For all possible configurations, refer to the UpgradePlan (Section 21.4.1, “UpgradePlan”) section.Deploying the
UpgradePlan
to theUpgrade Controller’s
namespace will begin theupgrade process
.NoteFor more information on the actual
upgrade process
, refer to How does the Upgrade Controller work? (Section 21.3, “How does the Upgrade Controller work?”).For information on how to track the
upgrade process
, refer to Tracking the upgrade process (Section 21.5, “Tracking the upgrade process”).