Update the Qovery Operator on a cluster
Queues an Engine v2 execution containing only the Qovery Operator Helm release. The chart version is required; the optional image version overrides the image target selected by q-core. The current Operator must be attached, connected, and protocol-compatible. A successful response means that the execution was accepted, not that Helm has completed. Cluster administrator permission is required.
Authorizations
JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' curl https://console.qovery.com/organization -H "Authorization: Bearer $qovery_token" '
Path Parameters
Organization ID
Cluster ID
Body
Response
The Qovery Operator update was queued
Identifier shared by the queued Engine execution and its infrastructure logs.
"00000000-0000-0000-0000-000000000001-0"
Operator image tag resolved for this execution.
"v1.204.0"
Operator Helm chart version resolved for this execution.
"0.2.2"