diff --git a/src/resources/OrganizationClusterRef.yaml b/src/resources/OrganizationClusterRef.yaml
index 2f8c3d63..04c20059 100644
--- a/src/resources/OrganizationClusterRef.yaml
+++ b/src/resources/OrganizationClusterRef.yaml
@@ -4,6 +4,10 @@ delete:
   parameters:
     - $ref: '../parameters/path/organizationId.yaml'
     - $ref: '../parameters/path/clusterId.yaml'
+    - in: query
+      name: deleteMode
+      schema:
+        $ref: '../schemas/enums/ClusterDeleteMode.yaml'
   tags:
     - Clusters
   responses:
diff --git a/src/schemas/enums/ClusterDeleteMode.yaml b/src/schemas/enums/ClusterDeleteMode.yaml
new file mode 100644
index 00000000..87360239
--- /dev/null
+++ b/src/schemas/enums/ClusterDeleteMode.yaml
@@ -0,0 +1,13 @@
+type: string
+description: | 
+  Indicates the mode to apply on cluster deletion  
+  **"hard delete"** means that we delete directly from our database, this is different from a **"trigger delete"** that cleans the resource
+  - `DEFAULT`: this is the normal way, trigger delete the cluster only if no environment linked to this cluster remains
+  - `DELETE_CLUSTER_AND_QOVERY_CONFIG`: hard delete environments linked to this cluster then trigger delete the cluster
+  - `DELETE_QOVERY_CONFIG`: hard delete environments linked to this cluster then hard delete the cluster
+enum:
+  - DEFAULT
+  - DELETE_CLUSTER_AND_QOVERY_CONFIG
+  - DELETE_QOVERY_CONFIG
+example: DEFAULT
+default: DEFAULT