Kibotos
API referencekibotos.ctrl.v1

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.

ctrl APICalled with an Operator certificate.How to call it

VolumeService owns the Native logical Volume lifecycle. Storage profile and host implementation details remain private to the runtime.

CreateVolume

POST/kibotos.ctrl.v1.VolumeService/CreateVolumeUnary
RequestCreateVolumeRequest
ResponseCreateVolumeResponse

GetVolume

POST/kibotos.ctrl.v1.VolumeService/GetVolumeUnary
RequestGetVolumeRequest
ResponseGetVolumeResponse

ListVolumes

POST/kibotos.ctrl.v1.VolumeService/ListVolumesUnary
RequestListVolumesRequest
  • page_sizeuint32= 1

    Zero selects the server default. Values above the server maximum are rejected rather than silently changed.

  • page_tokenstring= 2

    Opaque cursor returned by the preceding page.

  • By default, Volumes whose deletion has completed are omitted.

  • label_selectormap<string, string>= 4

    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.

ResponseListVolumesResponse

ResizeVolume

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.

POST/kibotos.ctrl.v1.VolumeService/ResizeVolumeUnary
RequestResizeVolumeRequest
  • volume_idstring= 2
  • The 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.

ResponseResizeVolumeResponse

DeleteVolume

POST/kibotos.ctrl.v1.VolumeService/DeleteVolumeUnary
RequestDeleteVolumeRequest
ResponseDeleteVolumeResponse

GetVolumeCommand

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.

POST/kibotos.ctrl.v1.VolumeService/GetVolumeCommandUnary
RequestGetVolumeCommandRequest
ResponseGetVolumeCommandResponse

VolumeCommand

VolumeCommandStatus

  • VOLUME_COMMAND_STATUS_UNSPECIFIED= 0
  • VOLUME_COMMAND_STATUS_PROCESSING= 1
  • VOLUME_COMMAND_STATUS_COMPLETED= 2

UpdateVolumeLabels

UpdateVolumeLabels and UpdateVolumeAnnotations follow the rules of their Workspace counterparts.

POST/kibotos.ctrl.v1.VolumeService/UpdateVolumeLabelsUnary
RequestUpdateVolumeLabelsRequest
ResponseUpdateVolumeLabelsResponse

UpdateVolumeAnnotations

POST/kibotos.ctrl.v1.VolumeService/UpdateVolumeAnnotationsUnary
RequestUpdateVolumeAnnotationsRequest
ResponseUpdateVolumeAnnotationsResponse

On this page