Mount Volumeset to Workload
mount_volumeset_to_workloadAttach a volumeset to a workload by adding a mount to its FIRST container. Additive: existing mounts and stored data stay as they are, a mount path already in use is refused, and a read-write-once volumeset another workload uses is refused; the workload rolls out again to pick up the mount. Creates the volumeset when missing; size/fileSystemType/performanceClass apply ONLY on that create path and are ignored when the volumeset already exists. Workload-type rule: ext4/xfs (read-write-once) volumesets require a stateful or vm workload and bind to ONE workload; shared-filesystem volumesets mount on any workload type.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"gvc": "<gvc>",
"workloadName": "<workloadName>"
},
"name": "mount_volumeset_to_workload"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| gvc | Yes | GVC name. | |
| org | No | Organization slug. | |
| size | No | Initial capacity in GB, CREATE-ONLY (ignored when the volumeset already exists; run_volumeset_command expandVolume grows it). Required when creating. Min 10 (200 for high-throughput-ssd), max 65536. | |
| tags | No | Optional tags for the volumeset; use them like Kubernetes labels for governance and search. | |
| mountPath | No | Mount path inside the container (defaults to /mnt/{volumesetName}). Normalized before validation (".." resolved, "//" collapsed); reserved paths /dev, /dev/log, /tmp, /var, /var/log are rejected. | |
| description | No | Volumeset description so operators know what data lives here (treat it like a Kubernetes annotation). | |
| workloadName | Yes | Existing workload name to mount storage into; pass the name only, not a link. | |
| volumesetName | No | Optional volumeset resource name, not a link. Omit to use {workloadName}-vol. If this volumeset does not exist yet, `size` is required so the tool can create it before mounting. | |
| fileSystemType | No | File system type — CREATE-ONLY (ignored when the volumeset already exists); default xfs. ext4/xfs are read-write-once (stateful or vm workloads only); shared is read-write-many (any workload type). | |
| performanceClass | No | Performance class — CREATE-ONLY (ignored when the volumeset already exists); default general-purpose-ssd. high-throughput-ssd requires size ≥ 200; shared pairs only with fileSystemType shared. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| data | No | The full result. Read this, not only the summary. | |
| details | No | ||
| summary | Yes | ||
| nextSteps | No |