Skip to main content
Version: 3.0

Upgrade Stork

You can upgrade Stork with or without Portworx Enterprise using the following methods:

Stork upgrade in non-airgapped environments​

To upgrade Stork to a version compatible with your Portworx Backup version (see the compatibility matrix for more information) alongside Portworx Enterprise, use the Portworx Operator method:

Portworx Operator method​

Perform the following steps to upgrade Stork using the Portworx Operator:

  1. Edit the stc (Kubernetes resource):

    kubectl edit stc <stc-name> -n <portworx-namespace>

  2. Change the Stork image and version details in Stork section:

    stork:
       args:
         webhook-controller: "true"
       enabled: true
       image: openstorage/stork:<stork-version>

  3. Save and exit.

If your environment has only a Portworx Backup deployment and no Portworx Enterprise, perform the steps in the following section to upgrade Stork to the latest supported version:

Non-Portworx deployment method​

To upgrade Stork using Daemonset method:

  1. Edit the deploy (Kubernetes resource):

    kubectl edit deploy stork -n <stork-namespace>

  2. Change the Stork image and version details in Stork section:

    image: openstorage/stork:<Variable name="stork_3.0.0"/>

  3. Save and exit.

Stork upgrade in air-gapped environment​

note

If you are planning to upgrade your Stork version to 25.2.0 on your air-gapped environment, ensure that you pull the following kopiaexecutor and nfsexecutor images from the docker paths and push them to your custom image registry:
docker.io/openstorage/kopiaexecutor:master-latest
docker.io/openstorage/nfsexecutor:master-latest

  1. If your application cluster is air-gapped, you must pull the following images before upgrading Stork. See the compatibility matrix for supported versions of Stork:

    Stork ImageVersion
    Storkopenstorage/stork26.3.0
    Command Executoropenstorage/cmdexecutor26.3.0
    NFS Executoropenstorage/nfsexecutor1.2.24
    Kopia Executoropenstorage/kopiaexecutor1.2.24
    note

    nfsExecutor and kopiaExecutor version 1.2.20 are not released or supported in Stork.

  2. You must then push the above images to your internal registry server, accessible by the air-gapped nodes.

  3. After pushing the images, follow the Portworx Operator method or Non-Portworx deployment method steps above based on your deployment to upgrade your Stork version.

Last updated on