Override the team's quota
Cluster admins only (`platform.admin`). Replaces the override; quantities it leaves out take the installation default. Workspaces that run keep running when the new quota is smaller; the next create, Sync or wake is checked against it. Audited as `team.quota`.
openapi/harthelm.yaml at v1.5.0__Host-harthelm_session<token>Browser session of the UI (12 h idle, 7 days absolute). State-changing requests also need the header
Harthelm-CSRF: 1 and a matching Origin.
team*integerNumeric resource id.
int641 <= valueapplication/json- body
Quantities to override; absent ones take the installation default. An empty object clears nothing (use DELETE).
1 <= propertiesrequests_cpu_millis?integerint641 <= valuerequests_memory_mib?integerint641 <= valuelimits_memory_mib?integerint641 <= valuestorage_gib?integerint641 <= valueThe quota.
application/json- response
default*override?Quantities to override; absent ones take the installation default. An empty object clears nothing (use DELETE).
1 <= propertieseffective*usage*updated_by?IDNumeric resource id.
int641 <= valueupdated_at?stringdate-timecurl -X PUT 'https://console.example.com/api/v1/teams/1/quota' \ -H 'Content-Type: application/json' \ -d '{}'{ "default": { "requests_cpu_millis": 0, "requests_memory_mib": 0, "limits_memory_mib": 0, "storage_gib": 0 }, "override": { "requests_cpu_millis": 1, "requests_memory_mib": 1, "limits_memory_mib": 1, "storage_gib": 1 }, "effective": { "requests_cpu_millis": 0, "requests_memory_mib": 0, "limits_memory_mib": 0, "storage_gib": 0 }, "usage": { "requests_cpu_millis": 0, "requests_memory_mib": 0, "limits_memory_mib": 0, "storage_gib": 0, "workspaces": 0, "awake_workspaces": 0, "held_by_deleted": { "workspaces": 0, "storage_gib": 0 } }, "updated_by": 1, "updated_at": "2019-08-24T14:15:22Z"}Move the team's workspace volumes to the current UID
Cluster admins only. After `security.defaultUid` changed, re-owns every workspace volume of the team that still belongs to another UID: each workspace stops, a root Job runs `chown -R <uid>:0`, `g=u` and setgid on directories on the node that holds the volume, and the workspace starts again under the new UID. Soft-deleted workspaces are included, their volumes still exist. Follow the Operation (kind `workspace.volume_owner`); it fails when a volume could not be re-owned, and that workspace keeps running as its old UID. Answers 409 when no volume of the team needs it or a migration of the team still runs.
Change a team's settings
`name` needs `team.manage` (409 `name-taken`, audited as `team.update`). `allow_run_as_user` is for cluster admins only: it lets the team's container services set `runAsUser`, root included; while it is on, the team's namespace enforces Pod Security `baseline` instead of `restricted`. Without it, every workspace pod runs as the UID that owns its volume and a Plan that sets `runAsUser` has the blocker `run-as-not-allowed`. Audited as `team.settings`. A deleting team answers 409 `team-deleting`.