Skip to main content
POST
Create a self-managed cluster run by the Qovery Operator

Authorizations

Authorization
string
header
required

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

organizationId
string<uuid>
required

Organization ID

Body

application/json
name
string
required
provider
enum<string>
required
Available options:
AWS
region
string
required
Example:

"eu-west-3"

credentials
object
required

AWS cloud credential of the organization that the cluster runs on. This operation only takes and returns its id.

platform
object
required

Platform template release and configuration of a new self-managed cluster. Set templateKey and templateVersion together to select a release, or omit both and Qovery selects its self-managed platform template release; only one of them answers 400. layerSelections and managedConfig are validated against the selected release, and {} gives that release with its default configuration. Send them without templateKey and templateVersion only if you already know the components of the self-managed platform template; a client that renders the fields of a release must send that release's coordinates, and selections of mandatory layers are rejected. The response returns the selected release, and the cluster keeps it even if Qovery later selects another one.

production
boolean
default:false
clusterInputs
object

String values keyed first by component key and then by input key

Response

Created self-managed cluster

id
string<uuid>
required
organizationId
string<uuid>
required
name
string
required
production
boolean
required
provider
enum<string>
required
Available options:
AWS,
SCW,
GCP,
DO,
AZURE,
OVH,
CIVO,
HETZNER,
ORACLE,
IBM,
ON_PREMISE
region
string
required
createdAt
string<date-time>
required
credentials
object
required

AWS cloud credential of the organization that the cluster runs on. This operation only takes and returns its id.

registry
object
required

Default ECR registry of the cluster, derived from its cloud credential and region.

platform
object
required

Platform template release selected for a cluster, with its layer selections and component configuration. Sensitive managedConfig values are redacted in responses.

clusterInputs
object
required

String values keyed first by component key and then by input key

layers
object[]
required