Upgrade

Upgrade the minor and patch version of your Solo UI components, or apply changes to the components’ configuration settings.

Considerations

Consider the following before you upgrade the Solo UI.

Test first: During an upgrade, the UI remains operational but might experience brief interruptions. Test the upgrade in a staging environment before upgrading your production environment.

Patch version upgrades: You can upgrade to any patch version within the same minor release directly.

Minor version upgrades: Do not skip minor versions. Upgrade one minor version at a time.

Multicluster upgrade order: In multicluster environments, always upgrade the management release in the management cluster before upgrading the relay releases in the connected clusters.

Upgrade the Solo UI

Single cluster

1. Save the Solo UI version that you want to upgrade to. You can find available versions in the version reference.

   export SOLO_UI_VERSION=0.4.8

2. Get the current Helm values for the management release.

   helm get values solo-management -n solo-enterprise -o yaml > management.yaml
   open management.yaml

3. Review your values and make any changes needed for the upgrade version. For breaking changes and new features, see the release notes.

4. Upgrade the management Helm release.

   warning

   Include your Helm values when you upgrade by using the –values, -f, or –set flags. Otherwise, any previous custom values might be overwritten.

   helm upgrade solo-management \
   oci://us-docker.pkg.dev/solo-public/solo-enterprise-helm/charts/management \
   -n solo-enterprise \
   --version ${SOLO_UI_VERSION} \
   -f management.yaml

5. Verify that all Solo UI component pods have a status of Running.

   kubectl get po -n solo-enterprise

   Example output:

   NAME                                    READY   STATUS    RESTARTS   AGE
   solo-enterprise-telemetry-collector-0   1/1     Running   0          4s
   solo-enterprise-ui-76c85c7d6b-xftcj     5/5     Running   0          4s
   solo-management-clickhouse-shard0-0     1/1     Running   0          4s
   

Multicluster

1. Save the Solo UI version that you want to upgrade to. You can find available versions in the version reference.

   export SOLO_UI_VERSION=0.4.8

2. Get the current Helm values for each release.

   helm get values solo-management -n solo-enterprise -o yaml --kube-context ${context1} > management.yaml
   helm get values solo-relay -n solo-enterprise -o yaml --kube-context ${context2} > relay.yaml

3. Review your values and make any changes needed for the upgrade version. For breaking changes and new features, see the release notes.

   open management.yaml
   open relay.yaml

4. Upgrade the management release.

   warning

   Always upgrade the management release in the management cluster before upgrading the relay releases in the connected clusters.
   Include your Helm values when you upgrade by using the –values, -f, or –set flags. Otherwise, any previous custom values might be overwritten.

   helm upgrade solo-management \
   oci://us-docker.pkg.dev/solo-public/solo-enterprise-helm/charts/management \
   -n solo-enterprise \
   --kube-context ${context1} \
   --version ${SOLO_UI_VERSION} \
   -f management.yaml

5. Verify that the UI management component pods have a status of Running.

   kubectl get po -n solo-enterprise --context ${context1}

   Example output:

   NAME                                    READY   STATUS    RESTARTS   AGE
   solo-enterprise-telemetry-collector-0   1/1     Running   0          4s
   solo-enterprise-ui-76c85c7d6b-xftcj     5/5     Running   0          4s
   solo-management-clickhouse-shard0-0     1/1     Running   0          4s
   

6. Upgrade the relay release in each connected cluster. Repeat for each connected cluster, updating the context each time.

   warning

   Include your Helm values when you upgrade by using the –values, -f, or –set flags. Otherwise, any previous custom values might be overwritten.

   helm upgrade solo-relay \
   oci://us-docker.pkg.dev/solo-public/solo-enterprise-helm/charts/relay \
   -n solo-enterprise \
   --kube-context ${context2} \
   --version ${SOLO_UI_VERSION} \
   -f relay.yaml

7. Verify that the relay component pods have a status of Running in each connected cluster.

   kubectl get po -n solo-enterprise --context ${context2}

   Example output:

   NAME                                     READY   STATUS    RESTARTS   AGE
   solo-enterprise-relay-5d7f668848-h456h   2/2     Running   0          13s
   solo-enterprise-telemetry-collector-0    1/1     Running   0          13s
   

Update your Solo Enterprise for Istio license

Before your Solo Enterprise for Istio license expires, update it by upgrading the Helm release with a new license key.

1. Get a new license key by contacting your account representative.

2. Save the new license key as an environment variable.

   export SOLO_ISTIO_LICENSE_KEY=<new-key-string>

3. Upgrade the management Helm release with the new license key. Use --reuse-values to preserve your existing configuration.

   helm upgrade solo-management \
   oci://us-docker.pkg.dev/solo-public/solo-enterprise-helm/charts/management \
   -n solo-enterprise \
   --reuse-values \
   --set licensing.licenseKey=${SOLO_ISTIO_LICENSE_KEY}

Upgrade Istio service meshes

To upgrade your Istio installations, see the upgrade guides for ambient mesh or sidecar mesh.