5.7 KiB

Raw Permalink Blame History

sidebar_label	title
Upgrade

import ClusterTarget from "!!raw-loader!@site/examples/upgrade/upgrade-cluster-target.yaml" import NodeSelector from "!!raw-loader!@site/examples/upgrade/upgrade-node-selector.yaml" import UpgradeForce from "!!raw-loader!@site/examples/upgrade/upgrade-force.yaml" import UpgradeRecovery from "!!raw-loader!@site/examples/upgrade/upgrade-recovery.yaml" import ManagedOSVersion from "!!raw-loader!@site/examples/upgrade/upgrade-managedos-version.yaml"

Upgrade

All components in Elemental are managed using Kubernetes. Below is how to use Kubernetes approaches to upgrade the components.

Elemental node upgrade

Elemental nodes are upgraded with the . Refer to the documentation for complete information.

Upgrade can be achieve either with CLI or UI:

Command Line Interface
User Interface

Upgrade via command line interface

There are two ways of selecting nodes for upgrading. Via a cluster target, which will match ALL nodes in a cluster that matches our selector or via node selector, which will match nodes based on the node labels. Node selector allows us to be more targeted with the upgrade while cluster selector just selects all the nodes in a matched cluster.

Updating an existing ManagedOSImage will trigger a new upgrade cycle, to reconcile the configured image (or image version) to all targeted nodes.

You can target nodes for an upgrade via a `clusterTarget` by setting it to the cluster name that you want to upgrade. All nodes in a cluster that matches that name will match and be upgraded.

{ClusterTarget}

You can target nodes for an upgrade via a `nodeSelector` by setting it to the label and value that you want to match. Any nodes containing that key with the value will match and be upgraded.

{NodeSelector}

When upgrading to an older version or the same version that is already running the upgrade-procedure will be skipped.

It is possible to force upgrades to older versions by setting the FORCE environment variable as shown below.

{UpgradeForce}

You can decide upgrade the Recovery partition when upgrading the system, or alternatively to upgrade the Recovery partition only.

{UpgradeRecovery}

Selecting source for upgrade

Just specify an OCI image on the osImage field

{ClusterTarget}

In this case we use the auto populated ManagedOSVersion resources to set the wanted managedOSVersionName field. See section Managing available versions to understand how the ManagedOSVersion are managed.

{ManagedOSVersion}

:::warning Warning If both osImage and ManagedOSVersion are defined in the same ManagedOSImage be aware that osImage takes precedence. :::

Managing available versions

It is possible to create ManagedOSVersions directly, or to subscribe to ManagedOSVersionChannels to automatically sync ManagedOSVersions from them.

For more details and a list of available channels, or to even make your own, please read the documentation.

Upgrade via user interface

To upgrade via the UI, you have to go in the Elemental Advanced menu, then click on Update Groups.

Choose a name, select clusters to target and choose between the two upgrade ways:

In this case, a OS Version Channels is used to auto populated OS Versions resources.

The channel bellow is provide by us but you can bring your own channel as well.

See section Managing available versions to understand how the ManagedOSVersion are managed.

After a short syncing time, you will see your OS Versions appears in the OS Versions menu.

Finally, you can select the OS Versions when you create your Upgrade Group according to the following screenshot:

Just specify an OCI image on the Image path field to upgrade to:

Click on the Create button to start the upgrade process, if you have multiple nodes, the upgrade will be done sequentially node by node.

5.7 KiB Raw Permalink Blame History