35 Edge 3.3 migration #

This section explains how to migrate your management and downstream clusters from Edge 3.2 to Edge 3.3.0.

Important

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

Always migrate to the Edge 3.3.0 release. For subsequent post-migration upgrades, refer to the management (Chapter 36, Management Cluster) and downstream (Chapter 37, Downstream clusters) cluster sections.

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

Table 35.1: Clusters and methods to upgrade downstream clusters #

Cluster type	Method
EIB provisioned clusters	See Section 35.1.3, “Fleet” for details.
Metal³ provisioned clusters	See Downstream cluster upgrades (Section 44.2, “Downstream cluster upgrades”) for details.
Phone-home provisioned clusters	See Upgrading the Kubernetes Version for Kubernetes version upgrade and Downstream clusters (Chapter 37, Downstream clusters) for SUC, Operating system, and other components.

35.1 Management Cluster #

This section covers the following topics:

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

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

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

35.1.1 Prerequisites #

35.1.1.1 Upgrade the Bare Metal Operator CRDs #

Note

Applies only to clusters that require a Chapter 10, Metal³ chart upgrade.

The Metal³ Helm chart includes the Bare Metal Operator (BMO) CRDs by leveraging Helm’s CRD directory.

However, this approach has certain limitations, particularly the inability to upgrade CRDs in this directory using Helm. For more information, refer to the Helm documentation.

As a result, before upgrading Metal³ to an Edge 3.3.0 compatible version, users must manually upgrade the underlying BMO CRDs.

On a machine with Helm installed and kubectl configured to point to your management cluster:

Manually apply the BMO CRDs:

helm show crds oci://registry.suse.com/edge/charts/metal3 --version 303.0.7+up0.11.5 | kubectl apply -f -

35.1.2 Upgrade Controller #

Important

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

The following topics are covered as part of this section:

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

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

35.1.2.1 Prerequisites #

35.1.2.1.1 Edge 3.3 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 Edge release.

To do this:

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

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

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

35.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.3.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.3.0

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

35.1.3 Fleet #

Note

Whenever possible, use the Section 35.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.3.0 release of the suse-edge/fleet-examples repository.
Charts scheduled for an upgrade must be upgraded to versions compatible with the Edge 3.3.0 release. For a list of the Edge 3.3.0 components, refer to Section 53.6, “Release 3.3.0”.

Important

To ensure a successful Edge 3.3.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 36.2, “Fleet”) documentation for a comprehensive guide on the steps required to perform a migration.

35.2 Downstream Clusters #

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

35.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.3.0 release of the suse-edge/fleet-examples repository.
Charts scheduled for an upgrade must be upgraded to versions compatible with the Edge 3.3.0 release. For a list of the Edge 3.3.0 components, refer to Section 53.6, “Release 3.3.0”.

Important

To ensure a successful Edge 3.3.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 37.1, “Fleet”) documentation for a comprehensive guide on the steps required to perform a migration.