Upgrade Stork

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

Stork upgrade in internet-connected environments

If you have to upgrade Stork 24.3.2 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-deployed-namespace>

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

   stork:
      args:
        webhook-controller: "true"
      enabled: true
      image: openstorage/stork:24.3.2

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-deployed-namespace>

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

   image: openstorage/stork:24.3.2

3. Save and exit.

Stork upgrade in air-gapped environment

1. If your application cluster is air-gapped, then you must pull the following openstorage images before upgrading Stork:

   2.7.3

   Image	Version
   openstorage/stork	24.3.2
   openstorage/cmdexecutor	24.3.2

   2.7.2

   Image	Version
   openstorage/stork	24.3.0
   openstorage/cmdexecutor	24.3.0

   2.7.1

   Image	Version
   openstorage/stork	24.2.1
   openstorage/cmdexecutor	24.2.1

   2.7.0

   Image	Version
   openstorage/stork	24.1.0
   openstorage/cmdexecutor	24.1.0

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.