Skip to main content
Version: 3.1

PVCs and Stork with Authorization

Creating volumes

Portwox authorization provides a method of protection for creating volumes through Kubernetes. Users must provide a token when requesting volumes in order to create a private volume. These tokens must be saved in a Secret, normally in the same namespace as the PVC.

The key in the Secret which holds the token must be named auth-token.

Then the annotations of the PVC can be used to point to the secret holding the token. The following table shows the annotation keys used to point to the secret:

NameDescription of the secret which has the token key which contains the namespace of the secret reference by auth-secret-name. If omitted, the namespace of the PVC will be used as default

Create a Secure PVC

  1. Find or create your token secret:

    For operator installs, a user token is automatically created and refreshed under px-user-token in your StorageCluster namespace.

    USER_TOKEN=$(kubectl get secrets px-user-token -n kube-system -o json | jq -r '.data["auth-token"]' | base64 -d)

    For all other configurations, create your own token secret:

    kubectl create secret generic px-user-token \
    -n kube-system --from-literal=auth-token=$USER_TOKEN
  2. Create a PVC request, specifying your volume size, accessModes, and authorizations:

    kind: PersistentVolumeClaim
    apiVersion: v1
    name: pvc-auth
    annotations: portworx-sc px-user-token default
    - ReadWriteOnce
    storage: 2Gi

For creation of secure CSI volumes, see Securing your CSI volumes.


When using CRDs consumed by Stork, you must use the same authorization model described above for the PVCs. Here is an example:

kind: VolumeSnapshot
name: mysql-snap1
annotations: px-user-token default
persistentVolumeClaimName: mysql-data


For more information on Kubernetes Secret which holds the environment variables See Kubernetes Secrets

Was this page helpful?