VolumeService
This page lists the methods of VolumeService in kibotos.ctrl.v1 with the messages and enums each one uses, generated from ctrl.proto and its comments. Those that several services use are on kibotos.ctrl.v1 types.
VolumeService owns the Native logical Volume lifecycle. Storage profile and host implementation details remain private to the runtime.
CreateVolume
/kibotos.ctrl.v1.VolumeService/CreateVolumeUnaryCreateVolumeRequestPersisted in the same transaction as the create command, with the rules and limits of Workspace.labels and Workspace.annotations. Both are included in idempotency.
CreateVolumeResponseGetVolume
/kibotos.ctrl.v1.VolumeService/GetVolumeUnaryListVolumes
/kibotos.ctrl.v1.VolumeService/ListVolumesUnaryListVolumesRequestZero selects the server default. Values above the server maximum are rejected rather than silently changed.
Opaque cursor returned by the preceding page.
By default, Volumes whose deletion has completed are omitted.
When non-empty, return only Volumes that carry every entry as a label with exactly that value. Keys and values must satisfy the label rules. A page token is only valid with the selector it was issued for.
ListVolumesResponseResizeVolume
ResizeVolume enlarges a Volume that is not mounted anywhere. The Volume keeps its ID, binding, mount path, and data; only its capacity moves, and only upward. A target equal to the current capacity is idempotent, a smaller one is invalid_argument, and a Volume that is still attached, or bound to a Workspace that holds an execution, is failed_precondition.
/kibotos.ctrl.v1.VolumeService/ResizeVolumeUnaryResizeVolumeRequestThe capacity the Volume must have when this call succeeds. It is an absolute target, not a delta, and it must be at least the capacity the Volume already has. It is required: a resize never resolves its own target from the storage profile.
ResizeVolumeResponseDeleteVolume
/kibotos.ctrl.v1.VolumeService/DeleteVolumeUnaryDeleteVolumeRequestDeleteVolumeResponseGetVolumeCommand
GetVolumeCommand returns the durable record of one Volume command: whether it is still processing and, once completed, its historical result. It is the query entry for a mutation whose response was lost.
/kibotos.ctrl.v1.VolumeService/GetVolumeCommandUnaryGetVolumeCommandRequestGetVolumeCommandResponseVolumeCommand
Canonical Connect code. A zero code on a processing command is not a completed success.
- One of
result
VolumeCommandStatus
VOLUME_COMMAND_STATUS_UNSPECIFIED= 0VOLUME_COMMAND_STATUS_PROCESSING= 1VOLUME_COMMAND_STATUS_COMPLETED= 2
UpdateVolumeLabels
UpdateVolumeLabels and UpdateVolumeAnnotations follow the rules of their Workspace counterparts.
/kibotos.ctrl.v1.VolumeService/UpdateVolumeLabelsUnaryUpdateVolumeLabelsRequestThe labels_revision the caller observed. Retries preserve this value.
The complete replacement; empty clears every label.
UpdateVolumeLabelsResponseUpdateVolumeAnnotations
/kibotos.ctrl.v1.VolumeService/UpdateVolumeAnnotationsUnaryUpdateVolumeAnnotationsRequestThe annotations_revision the caller observed. Retries preserve this value.
The complete replacement; empty clears every annotation.
UpdateVolumeAnnotationsResponseWorkspaceService
This page lists the methods of WorkspaceService in kibotos.ctrl.v1 with the messages and enums each one uses, generated from ctrl.proto and its comments. Those that several services use are on kibotos.ctrl.v1 types.
ExposureService
This page lists the methods of ExposureService in kibotos.ctrl.v1 with the messages and enums each one uses, generated from ctrl.proto and its comments. Those that several services use are on kibotos.ctrl.v1 types.