Portworx Stork

Portworx Stork is a storage scheduler for Kubernetes that helps achieve tighter integration of Portworx with Kubernetes. It allows users to co-locate pods with their data, provides seamless migration of pods in case of storage errors, and makes it easier to create and restore snapshots of Portworx volumes. Stork consists of 2 components, the Stork scheduler and an extender. Both of these components run in HA mode with 3 replicas by default. When Portworx is installed using the Portworx Enterprise Cluster Spec from Portworx Central , Stork is installed by default.

This topic describes how to verify Portworx Stork installation, upgrade Stork, and enable Stork telemetry.

Verify Stork Installation

Run the following command:

kubectl get pods -n portworx
...
stork-56f7c6d4cb-6b4tf                      1/1     Running    0              21h
stork-56f7c6d4cb-qs25p                      1/1     Running    0              21h
stork-56f7c6d4cb-v7q6b                      1/1     Running    0              21h
stork-scheduler-78c6dc7c6-bkglp             1/1     Running    0              21h
stork-scheduler-78c6dc7c6-lt8ql             1/1     Running    0              21h
stork-scheduler-78c6dc7c6-vwbmn             1/1     Running    0              21h
...

Upgrade Stork

Perform the following steps to upgrade Stork:

1. Edit the the storage cluster specification (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.

Enable Stork telemetry

When Portworx Enterprise telemetry is enabled, Stork logs are collected and uploaded to Pure1 telemetry. These logs assist in troubleshooting and observability of Stork operations.

For Stork log telemetry, the following requirements must be met:

• Portworx Operator version is 26.2.0 or later
• Stork version is 26.3.0 or later
• Telemetry is enabled

There is no flag to only disable Stork log telemetry. However, if even one of the requirements is not met, telemetry will not be enabled for Stork. You can configure the log-file-buffer-size-mib, log-file-max-backups and log-file-max-age parameters in the Stork section of the StorageCluster CR. For more information, see Stork configuration.

Limitations

• Stork-scheduler pod logs are not collected to /var/cores/portworx-bundle/stork/. For collecting stork-scheduler logs, you need to use the PortworxDiags CRD. For more information, see On-demand diagnostics using PortworxDiag custom resource.

For more information about Portworx telemetry, see Portworx Telemetry. For available Stork configuration options, see Stork configuration.