Use Stork with Portworx in airgapped EKS

Stork is the Portworx's storage scheduler for Kubernetes that helps achieve even tighter integration of Portworx with Kubernetes. It allows users to co-locate pods with their data, provides seamaless 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.

Install

When installing Portworx through the Portworx spec generator page in Portworx Central, Stork is installed by default along with Portworx.

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

Using Stork with your applications

To take advantage of the features of Stork, it needs to be used as the scheduler for your applications. On newer versions of stork this is enabled by default with the webhook controller when Stork is enabled.

If the webhook-controller is disabled, you need to specify Stork as the scheduler to be used when creating your applications. This can be done by adding schedulerName: stork to your application.

An example of a mysql deployment which uses Stork as the scheduler can be found here.

Snapshots with Stork

With Stork you can create and restore snapshots of Portworx volumes from Kubernetes. Instructions to perform these operations can be found here