---
title: "Record Cluster Provisioning Version"
method: PATCH
path: "/internal/clusters/{cluster_id}/provisioning-version"
tags: ["internal"]
---

# Record Cluster Provisioning Version

`PATCH /internal/clusters/{cluster_id}/provisioning-version`

## Request

- Base URL: `https://api.mengi.cloud` (the document declares no server; this is the origin it was published from)
- URL: `https://api.mengi.cloud/internal/clusters/{cluster_id}/provisioning-version`
- Auth: none declared. Required headers: `x-service-token`

Record the release a cluster without a version is provisioned with (internal).

A cluster created while no default version could be resolved has none,
and the worker picks the latest release for it. That choice must hold
across provisioning retries, or a retry after a newer release came out
would build its remaining servers on a different one. So the version is
only set while the record is empty, in one conditional UPDATE; the reply
is the version now on record, which the worker then builds with.

## Path parameters

- `cluster_id` string, uuid, required

## Headers

- `x-service-token` string, required

## Request body

- ClusterProvisioningVersionUpdate
  - `kubernetes_version` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/mengi/apis/mengi-cloud.md) · [All operations](https://skmtc.dev/mengi/apis/mengi-cloud/llms.txt) · [OpenAPI document](https://skmtc.dev/mengi/apis/mengi-cloud/revisions/4ae9b375cdbb?raw)