Cybus::Volume
Persistent storage for services.
A volume represents a storage space that can be associated with containers. Volumes allow data to be retained across service lifecycles, ensuring that files remain available even after services are disabled or removed.
This feature is only available in Docker Compose deployments of Connectware. It is not supported in Kubernetes deployments. Attempting to use this resource in a Kubernetes deployment will result in an error.
Lifecycle of a Volume
Creation: If the volume does not already exist when the service is enabled, Connectware automatically creates it.
Persistence: Once created, Connectware will not delete or truncate the volume. Neither when disabling the service nor at any other time.
Manual cleanup: Volumes remain in place even if services are installed, enabled, disabled, or removed. If you want to free up space, you must delete the volume manually.
This design ensures that volumes can be reused across different services and deployments, making them ideal for scenarios where persistent data storage is required.
Relationship to Files
Service commissioning files can also specify Cybus::File resources. These files are created inside the associated volume, allowing configuration or data files to be provisioned automatically during service setup.
Example
myVolume:
type: Cybus::Volume
Last updated
Was this helpful?