Applies to SUSE Edge 3.7

30 Edge 3.7 migration #

This section explains how to migrate your management and downstream clusters from SUSE Edge 3.6 to SUSE Edge 3.7.0.

Important

Always perform cluster migrations from the latest Z-stream release of SUSE Edge 3.6.

Always migrate to the SUSE Edge 3.7.0 release. For subsequent post-migration upgrades, refer to the management (Chapter 31, Management Cluster) and downstream (Chapter 32, Downstream clusters) cluster sections.

The following table lists the different types of clusters and the methods to upgrade clusters:

Table 30.1: Clusters and methods to upgrade downstream clusters #

Cluster type	Method
EIB provisioned clusters	See Section 30.1.3, “Fleet” for details.
Phone-home provisioned clusters	See Upgrading the Kubernetes Version for Kubernetes version upgrade and Downstream clusters (Chapter 32, Downstream clusters) for SUC, Operating system, and other components.

30.1 Management Cluster #

This section covers the following topics:

Section 30.1.1, “Prerequisites” - prerequisite steps to complete before starting the migration.

Section 30.1.2, “Upgrade Controller” - how to do a management cluster migration using the Chapter 19, Upgrade Controller.

Section 30.1.3, “Fleet” - how to do a management cluster migration using Chapter 6, Fleet.

30.1.1 Prerequisites #

30.1.2 Upgrade Controller #

Important

The Upgrade Controller currently supports SUSE Edge release migrations only for non air-gapped management clusters.

The following topics are covered as part of this section:

Section 30.1.2.1, “Prerequisites” - prerequisites specific to the Upgrade Controller.

Section 30.1.2.2, “Migration steps” - steps for migrating a management cluster to a new SUSE Edge version using the Upgrade Controller.

30.1.2.1 Prerequisites #

30.1.2.1.1 SUSE Edge 3.7 Upgrade Controller #

Before using the Upgrade Controller, you must first ensure that it is running a version that is capable of migrating to the desired SUSE Edge release.

To do this:

If you already have Upgrade Controller deployed from a previous SUSE Edge release, upgrade its chart:

helm upgrade upgrade-controller -n upgrade-controller-system oci://registry.suse.com/edge/charts/upgrade-controller --version 307.0.4+up0.1.3

If you do not have Upgrade Controller deployed, follow Section 19.3, “Installing the Upgrade Controller”.

30.1.2.2 Migration steps #

Performing a management cluster migration with the Upgrade Controller is fundamentally similar to executing an upgrade.

The only difference is that your UpgradePlan must specify the 3.7.0 release version:

apiVersion: lifecycle.suse.com/v1alpha1
kind: UpgradePlan
metadata:
  name: upgrade-plan-mgmt
  # Change to the namespace of your Upgrade Controller
  namespace: CHANGE_ME
spec:
  releaseVersion: 3.7.0

For information on how to use the above UpgradePlan to do a migration, refer to Upgrade Controller upgrade process (Section 31.1, “Upgrade Controller”).

30.1.3 Fleet #

Note

Whenever possible, use the Section 30.1.2, “Upgrade Controller” for migration.

Refer to this section only for use cases not covered by the Upgrade Controller.

Performing a management cluster migration with Fleet is fundamentally similar to executing an upgrade.

The key differences being that:

The fleets must be used from the release-3.7.0 release of the suse-edge/fleet-examples repository.
Charts scheduled for an upgrade must be upgraded to versions compatible with the SUSE Edge 3.7.0 release. For a list of the SUSE Edge 3.7.0 components, refer to Section 40.3, “Release 3.7.0”.

Important

To ensure a successful SUSE Edge 3.7.0 migration, it is important that users comply with the points outlined above.

Considering the points above, users can follow the management cluster Fleet (Section 31.2, “Fleet”) documentation for a comprehensive guide on the steps required to perform a migration.

30.2 Downstream Clusters #

Section 30.2.1, “Fleet” - how to do a downstream cluster migration using Chapter 6, Fleet.

30.2.1 Fleet #

Performing a downstream cluster migration with Fleet is fundamentally similar to executing an upgrade.

The key differences being that:

The fleets must be used from the release-3.7.0 release of the suse-edge/fleet-examples repository.
Charts scheduled for an upgrade must be upgraded to versions compatible with the SUSE Edge 3.7.0 release. For a list of the SUSE Edge 3.7.0 components, refer to Section 40.3, “Release 3.7.0”.

Important

To ensure a successful SUSE Edge 3.7.0 migration, it is important that users comply with the points outlined above.

Considering the points above, users can follow the downstream cluster Fleet (Section 32.1, “Fleet”) documentation for a comprehensive guide on the steps required to perform a migration.