Storage

Pods on Plexivo Kubernetes keep data across restarts in persistent volumes. You ask for one with a PersistentVolumeClaim, and Plexivo creates the volume for it.

How much you can use#

When you create a workload with Advanced: YAML, Helm or Git, set its Storage under Capacity per pod, in steps of 5 GB, up to 500 GB. Your claims together may request up to that amount. A workload made with Deploy a container starts with none. To change it later, use the API: see Change the requested capacity. The workload’s Overview shows each volume and how much is used.

Claim a volume#

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: data
spec:
  accessModes: ["ReadWriteOnce"]
  resources:
    requests:
      storage: 10Gi

Then mount it in your pod with a persistentVolumeClaim volume. For a StatefulSet, use volumeClaimTemplates and each replica gets its own volume.

• Leave out storageClassName and volumeName: Plexivo provisions the volume. A claim may not name an existing volume.
• A claim’s data source, if you clone one, must be in your own namespace.

Billing#

Storage is billed by the GB, for each claim a running pod mounts, plus any ephemeral storage its containers request. A claim shared by several pods is counted once.

Before you delete#

Deleting a workload removes its namespace, with its volume claims. Copy out any data you want to keep first.

Next steps#