WorkspaceService

本页列出 kibotos.ctrl.v1 中 WorkspaceService 的方法及每个方法用到的消息与枚举，由 ctrl.proto 及其注释生成，注释保持英文。多个服务共用的消息与枚举见 kibotos.ctrl.v1 类型。

WorkspaceService owns the Native Workspace lifecycle and stable identity.

CreateWorkspace复制标题链接

Accepts a durable creation command. CREATING is an accepted result; execution continues without client requests. Query GetWorkspaceCommand for completion, or replay the same input/command ID to recover acceptance.

GetWorkspace复制标题链接

ListWorkspaces复制标题链接

UpdateWorkspaceExpiration复制标题链接

GetWorkspaceCommand复制标题链接

WorkspaceCommand复制标题链接

WorkspaceCommandStatus复制标题链接

StopWorkspace复制标题链接

StopMode复制标题链接

StopMode selects how a Workspace stops. The zero value is the normal stop, which succeeds only after the guest confirms writeback. FORCE is an explicit caller decision: it does not wait for guest writers, gives the guest one short best-effort sync, and stops the execution; the most recent writes may be lost.

StartWorkspace复制标题链接

Accepts a durable start command with the same completion semantics as CreateWorkspace.

UpdateWorkspaceNetworkPolicy复制标题链接

UpdateWorkspaceNetworkPolicy replaces the expected policy. A non-zero expected_revision must equal the current revision or the call is aborted and nothing changes, even when the content is equal. Equal content is idempotent and keeps the revision. Different content on an AVAILABLE Workspace increments the revision and returns once the running execution confirmed or failed the change; on a STOPPED Workspace it only records the expectation for the next start. Any other state is failed_precondition. On an AVAILABLE Workspace whose execution still uses the DNS configuration it was started with by an earlier release, a policy that references a Resolver is failed_precondition and neither the expected nor the applied policy changes; the Workspace accepts it after a stop and start.

UpdateWorkspaceMemory复制标题链接

UpdateWorkspaceMemory replaces the memory the Workspace requests for its next execution. It only records configuration: it never starts, stops, or resizes a running execution, and the new value takes effect at the next successful start. It is accepted by a Workspace that holds no execution: STOPPED, and the FAILED a start is allowed to resume from, so a request no placement could honour can be lowered again. Any other state is failed_precondition. The same value is idempotent and keeps the revision, a different value increments it, and capacity is judged by that later start, not by this call.

UpdateWorkspaceCpu复制标题链接

UpdateWorkspaceCpu replaces the CPU the Workspace requests for its next execution. It follows every rule of UpdateWorkspaceMemory: configuration only, accepted by a Workspace that holds no execution, the same value is idempotent and keeps the revision, and capacity is judged by the later start. Both share one resources_revision, so a CPU change and a memory change submitted against the same revision conflict rather than both landing.

ResizeWorkspaceWritableLayer复制标题链接

ResizeWorkspaceWritableLayer enlarges the Workspace's writable filesystem layer in place. The Workspace keeps its identity, Template binding, Volume binding, and every byte already written to the layer; nothing is started, stopped, or rebuilt. The target is absolute and only moves upward: equal to the current capacity it is a plain success that opens no command, smaller it is invalid_argument, and beyond what the placement can hold it is resource_exhausted. It is accepted by a Workspace that holds no execution, under the same rule as UpdateWorkspaceMemory. A Workspace whose layer does not exist yet only records the capacity; the layer is created at that size on its first start.

UpdateWorkspaceVolumeBinding复制标题链接

UpdateWorkspaceVolumeBinding replaces the Workspace's Volume binding with the complete target it is given: NONE releases the current Volume, BOUND with the current Volume changes its mount path or delete_with_workspace, and BOUND with another Volume binds that one and releases the current one. NEW is not accepted here. It only records configuration: nothing is started, stopped, or rebuilt, and the new binding is mounted by the next successful start. A released Volume always survives with its data and returns to AVAILABLE. It is accepted by a Workspace that holds no execution, under the same rule as UpdateWorkspaceMemory; the target Volume must be AVAILABLE, unbound, and reachable from the placement this Workspace already has. The same binding is idempotent and keeps binding_revision, a different one increments it.

RevokeWorkspaceDataPlane复制标题链接

RevokeWorkspaceDataPlane invalidates all existing data-plane credentials without restarting the Workspace or exposing its internal route target.

DeleteWorkspace复制标题链接

UpdateWorkspaceLabels复制标题链接

UpdateWorkspaceLabels replaces the complete label map; it never merges. expected_revision must equal labels_revision or the call is aborted and nothing changes. Content equal to the stored labels succeeds and keeps the revision. Accepted in every state except DELETED.

UpdateWorkspaceAnnotations复制标题链接

UpdateWorkspaceAnnotations follows every rule of UpdateWorkspaceLabels for the annotation map and annotations_revision.