ClusterMaintenance

Plan a rolling upgrade

Changed on

Resolves the target with the image list of the configurator (patch, next-minor, next-lts, next-major, last-lts, version) from the line the nodes run and describes the steps, the target release, what prov-db-image declares afterwards and the warnings. Nothing is changed.

get/api/clusters/{clusterName}/actions/rolling/upgrade/plan

Request

  • The document declares no server URL.
  • Auth
    none declared. Required headers: Authorization

Path parameters

clusterNamestring required

Cluster Name

Query parameters

target'patch' | 'next-minor' | 'next-lts' | 'next-major' | 'last-lts' | 'previous-minor' | 'previous-major' | 'version'

patch (default), next-minor, next-lts, next-major, last-lts, previous-minor, previous-major, version

versionstring

with target=version: the release or line to move to

Headers

Authorizationstring required

Insert your access token

Response

OK

clusterstring
currentImagestring

prov-db-image as declared

currentIsLTSboolean
currentLinestring
currentReleasestring

the release the service definitions carry (prov-db-docker-img-resolved)

declaredAfterstring

prov-db-image after the upgrade

flavorstring
imageListstring
mechanicstring

"upgrade" (restart on the new image) or "reprov" (provision again + reseed)

nodesobject[]
orchestratorstring
orderstring[]
statusstring
stepsstring[]
targetstring
targetImagestring

the real release, repo:x.y.z

targetIsLTSboolean
targetLinestring
warningsstring[]

Changes