Skip to main content
Version: 2.7

Upgrade Stork

Upgrade Stork

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

Upgrade Method with or without Portworx Enterprise

If you have to upgrade Stork 24.1.0 along with Portworx Enterprise, you can opt-in for Daemonset upgrade or Portworx Operator upgrade:

Portworx DaemonSet method

To upgrade Stork using Daemonset method:

  1. Edit the deploy (Kubernetes resource):

    kubectl edit stork deploy -n <portworx-deployed-namespace>
  2. Change the Stork image and version details in Stork section:

    image: openstorage/stork:24.1.0
  3. Save and exit.

Portworx Operator method

Perform the below steps for Stork upgrade using Portworx operator option:

  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.1.0
  3. Save and exit.

Stork upgrade for air-gapped environments

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

  • openstorage/cmdexecutor:24.1.0
  • openstorage/stork:24.1.0
  1. You must then push the above images to your internal registry server, accessible by the air-gapped nodes.

  2. 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.

Was this page helpful?