Skip to main content
Version: 2.10

Upgrade Stork

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

Stork upgrade in non-airgapped environments​

If you have to upgrade Stork to the version compatible with your Portworx Backup version (refer to the compatibility matrix for more information) along with Portworx Enterprise, you can opt-in for Portworx Operator method of upgrade:

Portworx Operator method​

Perform the below steps to upgrade Stork using Portworx operator way:

  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:25.6.1

  3. Save and exit.

If your environment has only Portworx Backup deployment and no Portworx then perform the steps in the following topic 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: 25.6.1

  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, then you must pull the below images before upgrading Stork. Refer to compatibility matrix for supported versions of Stork:

    Stork ImageVersion
    Storkopenstorage/stork25.6.1
    Command Executoropenstorage/cmdexecutor25.5.0
    NFS Executoropenstorage/nfsexecutor1.2.22
    Kopia Executoropenstorage/kopiaexecutor1.2.22
    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 instructions in Upgrade Stork section at the top of this page based on your deployment methods to upgrade your Stork version.