Overview
The Delete Cluster endpoint permanently removes GPU clusters and all associated resources. This operation is irreversible and includes options for data backup, billing finalization, and cleanup of related resources like snapshots and network configurations.Endpoint
Path Parameters
Parameter | Type | Required | Description |
---|---|---|---|
cluster_id | string | Yes | Unique cluster identifier |
Request Body
Parameter | Type | Required | Description |
---|---|---|---|
force | boolean | No | Force delete without graceful shutdown (default: false) |
create_final_snapshot | boolean | No | Create final snapshot before deletion (default: false) |
snapshot_name | string | No | Custom name for final snapshot |
preserve_snapshots | boolean | No | Keep existing snapshots after cluster deletion (default: true) |
delete_snapshots | boolean | No | Delete all associated snapshots (default: false) |
finalize_billing | boolean | No | Finalize billing and generate final invoice (default: true) |
cleanup_network_resources | boolean | No | Remove security groups and network configs (default: true) |
wait_for_completion | boolean | No | Wait for complete deletion (default: false) |
timeout_minutes | integer | No | Maximum wait time for completion (default: 10, max: 30) |
deletion_reason | string | No | Reason for deletion (for audit logs) |
confirm_deletion | string | No | Must be “DELETE” to confirm permanent deletion |
Request Examples
Response Schema
Deletion Progress Phases
Phase | Description | Typical Duration |
---|---|---|
stopping_cluster | Gracefully stopping all running processes | 1-5 minutes |
creating_final_snapshot | Creating final backup snapshot (if requested) | 2-10 minutes |
finalizing_billing | Processing final billing and generating invoice | 30-60 seconds |
cleaning_storage | Removing storage volumes and data (except preserved) | 1-3 minutes |
cleaning_network | Removing network resources and security groups | 30-60 seconds |
cleaning_compute | Releasing GPU and compute resources | 30-60 seconds |
updating_records | Updating database records and audit logs | 10-30 seconds |
completed | Deletion process finished | - |
Use Cases
Project Completion Cleanup
Clean up all resources when a project is completed.Cost Optimization Cleanup
Delete expensive idle clusters to reduce costs.Emergency Security Cleanup
Quickly delete clusters in response to security incidents.Error Handling
Security Considerations
- Permanent Operation: Cluster deletion is irreversible - ensure proper confirmation
- Data Security: Consider data sensitivity when choosing snapshot preservation options
- Access Control: Verify deletion permissions, especially for shared clusters
- Audit Logging: All deletions are logged for compliance and security auditing
- Emergency Procedures: Have emergency deletion procedures for security incidents
Best Practices
- Backup Important Data: Always create final snapshots for critical workloads
- Staged Deletion: Delete development clusters first, then production
- Cost Tracking: Monitor deletion savings and optimize deletion strategies
- Security Compliance: Follow data retention policies and regulatory requirements
- Documentation: Document deletion reasons for audit trails
- Automation: Implement automated cleanup for idle or completed workloads
Authorizations
API key authentication. Use 'Bearer YOUR_API_KEY' format.
Path Parameters
Unique identifier of the cluster to delete
Response
Cluster deleted successfully