Volumes

Koyeb volumes are block storage devices that can be provisioned to provide persistent storage across deployments. Unlike the local ephemeral storage available for Instances, volume storage can be reattached to new deployments, saving important context and configuration that would otherwise be lost.

Create a volume

When creating a volume, you can set its name, its size and its region.

To create a Volume, click Volumes (opens in a new tab) in the Koyeb control panel and select Create volume.

Limitations

Koyeb volumes are currently in public preview and have the following limitations.

• Region limitation: Volumes are currently only available in the Washington, D.C. (was) and Frankfurt (fra) regions.
• Size limitation: At present, volumes must be between 1 and 10 Gigabytes in size.

Attach a Volume

You can attach a volume to a new or existing Service.

Each Volume you create is scoped to a region, so a Volume must be attached to a Service running in the same region.

Redeployment downtime

The introduction of volumes introduces a stateful component to the deployment workflow. This means that Services that have volumes attached may experience downtime during redeployment while the volume is detached from the previous deployment and attached to the new deployment.

Limitations

Koyeb volumes are currently in public preview and have the following limitations.

• Scale limitation: Volumes currently only work with Services with a scale of one.
• Instance limitation: Volumes can only be attached to standard and GPU Services. You cannot attach a volume to eco-* or free Instance. Learn more about the different types of Instances available on the Instance reference page.

Volume mobility

At the moment, once a volume is attached to a Service, it cannot currently be detached except if the Service is deleted. The Volume can't be attached to another Service.

To move data between Services, you should leverage Snapshots to copy your data and create a new volume from the copy.

Volume statuses

A volume can have 2 statuses:

• Detached: the Volume has not yet been attached or was detached after Service deletion.
• Attached: the Volume is currently attached to a Service.

Data loss

Volumes are local and as such they might fail as they are bound to a single machine. You must rely on Snapshots to minimize the prevent data loss You need to rely on a distributed software to maintain high-availability and prevent data loss. Keep in mind that there is no redundancy here and fault-tolerance is on you.