---
title: "Changes to Create database cluster"
method: POST
path: "/namespaces/{namespace}/database-clusters"
---

# Changes to Create database cluster

`POST /namespaces/{namespace}/database-clusters`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 17 of 50 revisions.

- **2026-07-17** `46b19e13670b`: 16 info
- **2026-04-13** `2e766357dc4d`: 4 info
- **2025-12-18** `7b1e5ed00522`: 9 warning, 7 info
- **2025-11-20** `497dc326c61a`: 4 breaking, 20 info
- **2025-09-15** `c353211f18a1`: 4 info
- **2025-07-09** `db26d5a4ee2d`: 8 info
- **2025-05-19** `edeafc325979`: 4 info
- **2025-03-28** `46a77c66fedf`: 4 info
- **2025-03-25** `d18481a20594`: 8 info
- **2025-03-07** `d2b416199d3e`: 3 breaking, 1 info
- **2025-01-28** `d859b07bf00c`: 20 warning
- **2024-12-18** `053777ddd4cc`: 20 info
- **2024-08-30** `64882bb17b93`: 4 info
- **2024-08-29** `0e0e93d42e4b`: 4 info
- **2024-06-19** `00f3dd8cb624`: 2 info
- **2024-04-18** `acf5c42a114b`: 12 info
- **2024-04-12** `dec31e5eea8e`: 4 breaking, 76 warning, 18 info

## Changes

- **2026-07-17** `46b19e13670b`: 16 info
  - added the new optional request property `spec/engine/resources/limits`
  - added the new optional request property `spec/engine/resources/requests`
  - added the new optional request property `spec/proxy/resources/limits`
  - added the new optional request property `spec/proxy/resources/requests`
  - added the optional property `spec/engine/resources/limits` to the response with the `200` status
  - added the optional property `spec/engine/resources/limits` to the response with the `201` status
  - added the optional property `spec/engine/resources/limits` to the response with the `202` status
  - added the optional property `spec/engine/resources/requests` to the response with the `200` status
  - added the optional property `spec/engine/resources/requests` to the response with the `201` status
  - added the optional property `spec/engine/resources/requests` to the response with the `202` status
  - added the optional property `spec/proxy/resources/limits` to the response with the `200` status
  - added the optional property `spec/proxy/resources/limits` to the response with the `201` status
  - added the optional property `spec/proxy/resources/limits` to the response with the `202` status
  - added the optional property `spec/proxy/resources/requests` to the response with the `200` status
  - added the optional property `spec/proxy/resources/requests` to the response with the `201` status
  - added the optional property `spec/proxy/resources/requests` to the response with the `202` status
- **2026-04-13** `2e766357dc4d`: 4 info
  - added the new optional request property `spec/proxy/storage`
  - added the optional property `spec/proxy/storage` to the response with the `200` status
  - added the optional property `spec/proxy/storage` to the response with the `201` status
  - added the optional property `spec/proxy/storage` to the response with the `202` status
- **2025-12-18** `7b1e5ed00522`: 9 warning, 7 info
  - added the new `ClusterIP` enum value to the `spec/proxy/expose/type` response property for the response status `200`
  - added the new `ClusterIP` enum value to the `spec/proxy/expose/type` response property for the response status `201`
  - added the new `ClusterIP` enum value to the `spec/proxy/expose/type` response property for the response status `202`
  - added the new `LoadBalancer` enum value to the `spec/proxy/expose/type` response property for the response status `200`
  - added the new `LoadBalancer` enum value to the `spec/proxy/expose/type` response property for the response status `201`
  - added the new `LoadBalancer` enum value to the `spec/proxy/expose/type` response property for the response status `202`
  - added the new `NodePort` enum value to the `spec/proxy/expose/type` response property for the response status `200`
  - added the new `NodePort` enum value to the `spec/proxy/expose/type` response property for the response status `201`
  - added the new `NodePort` enum value to the `spec/proxy/expose/type` response property for the response status `202`
  - the `type` request property default value changed from `internal` to `ClusterIP`
  - added the new `ClusterIP` enum value to the request property `spec/proxy/expose/type`
  - added the new `LoadBalancer` enum value to the request property `spec/proxy/expose/type`
  - added the new `NodePort` enum value to the request property `spec/proxy/expose/type`
  - the `type` response's property default value changed from `internal` to `ClusterIP` for the status `200`
  - the `type` response's property default value changed from `internal` to `ClusterIP` for the status `201`
  - the `type` response's property default value changed from `internal` to `ClusterIP` for the status `202`
- **2025-11-20** `497dc326c61a`: 4 breaking, 20 info
  - the request property `spec/dataSource/dataImport/source/path` became required
  - the request property `spec/dataSource/dataImport/source/s3/bucket` became required
  - the request property `spec/dataSource/dataImport/source/s3/endpointURL` became required
  - the request property `spec/dataSource/dataImport/source/s3/region` became required
  - added the new optional request property `spec/engineFeatures`
  - added the new optional request property `status/engineFeatures`
  - added the optional property `spec/engineFeatures` to the response with the `200` status
  - added the optional property `spec/engineFeatures` to the response with the `201` status
  - added the optional property `spec/engineFeatures` to the response with the `202` status
  - added the optional property `status/engineFeatures` to the response with the `200` status
  - added the optional property `status/engineFeatures` to the response with the `201` status
  - added the optional property `status/engineFeatures` to the response with the `202` status
  - the response property `spec/dataSource/dataImport/source/path` became required for the status `200`
  - the response property `spec/dataSource/dataImport/source/path` became required for the status `201`
  - the response property `spec/dataSource/dataImport/source/path` became required for the status `202`
  - the response property `spec/dataSource/dataImport/source/s3/bucket` became required for the status `200`
  - the response property `spec/dataSource/dataImport/source/s3/bucket` became required for the status `201`
  - the response property `spec/dataSource/dataImport/source/s3/bucket` became required for the status `202`
  - the response property `spec/dataSource/dataImport/source/s3/endpointURL` became required for the status `200`
  - the response property `spec/dataSource/dataImport/source/s3/endpointURL` became required for the status `201`
  - the response property `spec/dataSource/dataImport/source/s3/endpointURL` became required for the status `202`
  - the response property `spec/dataSource/dataImport/source/s3/region` became required for the status `200`
  - the response property `spec/dataSource/dataImport/source/s3/region` became required for the status `201`
  - the response property `spec/dataSource/dataImport/source/s3/region` became required for the status `202`
- **2025-09-15** `c353211f18a1`: 4 info
  - added the new optional request property `spec/proxy/expose/loadBalancerConfigName`
  - added the optional property `spec/proxy/expose/loadBalancerConfigName` to the response with the `200` status
  - added the optional property `spec/proxy/expose/loadBalancerConfigName` to the response with the `201` status
  - added the optional property `spec/proxy/expose/loadBalancerConfigName` to the response with the `202` status
- **2025-07-09** `db26d5a4ee2d`: 8 info
  - added the new optional request property `spec/dataSource/dataImport`
  - added the new optional request property `status/dataImportJobName`
  - added the optional property `spec/dataSource/dataImport` to the response with the `200` status
  - added the optional property `spec/dataSource/dataImport` to the response with the `201` status
  - added the optional property `spec/dataSource/dataImport` to the response with the `202` status
  - added the optional property `status/dataImportJobName` to the response with the `200` status
  - added the optional property `status/dataImportJobName` to the response with the `201` status
  - added the optional property `status/dataImportJobName` to the response with the `202` status
- **2025-05-19** `edeafc325979`: 4 info
  - added the new optional request property `spec/podSchedulingPolicyName`
  - added the optional property `spec/podSchedulingPolicyName` to the response with the `200` status
  - added the optional property `spec/podSchedulingPolicyName` to the response with the `201` status
  - added the optional property `spec/podSchedulingPolicyName` to the response with the `202` status
- **2025-03-28** `46a77c66fedf`: 4 info
  - added the new optional request property `status/conditions`
  - added the optional property `status/conditions` to the response with the `200` status
  - added the optional property `status/conditions` to the response with the `201` status
  - added the optional property `status/conditions` to the response with the `202` status
- **2025-03-25** `d18481a20594`: 8 info
  - added the new optional request property `spec/monitoring/resources/claims/items/request`
  - added the new optional request property `status/observedGeneration`
  - added the optional property `spec/monitoring/resources/claims/items/request` to the response with the `200` status
  - added the optional property `spec/monitoring/resources/claims/items/request` to the response with the `201` status
  - added the optional property `spec/monitoring/resources/claims/items/request` to the response with the `202` status
  - added the optional property `status/observedGeneration` to the response with the `200` status
  - added the optional property `status/observedGeneration` to the response with the `201` status
  - added the optional property `status/observedGeneration` to the response with the `202` status
- **2025-03-07** `d2b416199d3e`: 3 breaking, 1 info
  - the response property `spec/backup/enabled` became optional for the status `200`
  - the response property `spec/backup/enabled` became optional for the status `201`
  - the response property `spec/backup/enabled` became optional for the status `202`
  - the request property `spec/backup/enabled` became optional
- **2025-01-28** `d859b07bf00c`: 20 warning
  - removed the request property `spec/engine/affinity`
  - removed the request property `spec/monitoring/resources/claims/items/request`
  - removed the request property `spec/proxy/affinity`
  - removed the request property `spec/sharding/configServer/affinity`
  - removed the request property `status/observedGeneration`
  - removed the optional property `spec/engine/affinity` from the response with the `200` status
  - removed the optional property `spec/engine/affinity` from the response with the `201` status
  - removed the optional property `spec/engine/affinity` from the response with the `202` status
  - removed the optional property `spec/monitoring/resources/claims/items/request` from the response with the `200` status
  - removed the optional property `spec/monitoring/resources/claims/items/request` from the response with the `201` status
  - removed the optional property `spec/monitoring/resources/claims/items/request` from the response with the `202` status
  - removed the optional property `spec/proxy/affinity` from the response with the `200` status
  - removed the optional property `spec/proxy/affinity` from the response with the `201` status
  - removed the optional property `spec/proxy/affinity` from the response with the `202` status
  - removed the optional property `spec/sharding/configServer/affinity` from the response with the `200` status
  - removed the optional property `spec/sharding/configServer/affinity` from the response with the `201` status
  - removed the optional property `spec/sharding/configServer/affinity` from the response with the `202` status
  - removed the optional property `status/observedGeneration` from the response with the `200` status
  - removed the optional property `status/observedGeneration` from the response with the `201` status
  - removed the optional property `status/observedGeneration` from the response with the `202` status
- **2024-12-18** `053777ddd4cc`: 20 info
  - added the new optional request property `spec/engine/affinity`
  - added the new optional request property `spec/monitoring/resources/claims/items/request`
  - added the new optional request property `spec/proxy/affinity`
  - added the new optional request property `spec/sharding/configServer/affinity`
  - added the new optional request property `status/observedGeneration`
  - added the optional property `spec/engine/affinity` to the response with the `200` status
  - added the optional property `spec/engine/affinity` to the response with the `201` status
  - added the optional property `spec/engine/affinity` to the response with the `202` status
  - added the optional property `spec/monitoring/resources/claims/items/request` to the response with the `200` status
  - added the optional property `spec/monitoring/resources/claims/items/request` to the response with the `201` status
  - added the optional property `spec/monitoring/resources/claims/items/request` to the response with the `202` status
  - added the optional property `spec/proxy/affinity` to the response with the `200` status
  - added the optional property `spec/proxy/affinity` to the response with the `201` status
  - added the optional property `spec/proxy/affinity` to the response with the `202` status
  - added the optional property `spec/sharding/configServer/affinity` to the response with the `200` status
  - added the optional property `spec/sharding/configServer/affinity` to the response with the `201` status
  - added the optional property `spec/sharding/configServer/affinity` to the response with the `202` status
  - added the optional property `status/observedGeneration` to the response with the `200` status
  - added the optional property `status/observedGeneration` to the response with the `201` status
  - added the optional property `status/observedGeneration` to the response with the `202` status
- **2024-08-30** `64882bb17b93`: 4 info
  - added the new optional request property `spec/sharding`
  - added the optional property `spec/sharding` to the response with the `200` status
  - added the optional property `spec/sharding` to the response with the `201` status
  - added the optional property `spec/sharding` to the response with the `202` status
- **2024-08-29** `0e0e93d42e4b`: 4 info
  - added the new optional request property `status/details`
  - added the optional property `status/details` to the response with the `200` status
  - added the optional property `status/details` to the response with the `201` status
  - added the optional property `status/details` to the response with the `202` status
- **2024-06-19** `00f3dd8cb624`: 2 info
  - api tag `Database Cluster` added
  - api tag `databaseCluster` removed
- **2024-04-18** `acf5c42a114b`: 12 info
  - added the new optional request property `spec/engine/crVersion`
  - added the new optional request property `status/crVersion`
  - added the new optional request property `status/recommendedCRVersion`
  - added the optional property `spec/engine/crVersion` to the response with the `200` status
  - added the optional property `spec/engine/crVersion` to the response with the `201` status
  - added the optional property `spec/engine/crVersion` to the response with the `202` status
  - added the optional property `status/crVersion` to the response with the `200` status
  - added the optional property `status/crVersion` to the response with the `201` status
  - added the optional property `status/crVersion` to the response with the `202` status
  - added the optional property `status/recommendedCRVersion` to the response with the `200` status
  - added the optional property `status/recommendedCRVersion` to the response with the `201` status
  - added the optional property `status/recommendedCRVersion` to the response with the `202` status
- **2024-04-12** `dec31e5eea8e`: 4 breaking, 76 warning, 18 info
  - the request property `spec/backup/enabled` became required
  - removed the enum value `ClusterIP` of the request property `spec/proxy/expose/type`
  - removed the enum value `LoadBalancer` of the request property `spec/proxy/expose/type`
  - removed the enum value `NodePort` of the request property `spec/proxy/expose/type`
  - removed the request property `spec/dataSource/dataImport`
  - removed the request property `spec/engine/crVersion`
  - removed the request property `spec/engine/resources/limits`
  - removed the request property `spec/engine/resources/requests`
  - removed the request property `spec/engineFeatures`
  - removed the request property `spec/monitoring/resources/claims/items/request`
  - removed the request property `spec/podSchedulingPolicyName`
  - removed the request property `spec/proxy/expose/loadBalancerConfigName`
  - removed the request property `spec/proxy/resources/limits`
  - removed the request property `spec/proxy/resources/requests`
  - removed the request property `spec/proxy/storage`
  - removed the request property `spec/sharding`
  - removed the request property `status/conditions`
  - removed the request property `status/crVersion`
  - removed the request property `status/dataImportJobName`
  - removed the request property `status/details`
  - removed the request property `status/engineFeatures`
  - removed the request property `status/observedGeneration`
  - removed the request property `status/recommendedCRVersion`
  - removed the optional property `spec/dataSource/dataImport` from the response with the `200` status
  - removed the optional property `spec/dataSource/dataImport` from the response with the `201` status
  - removed the optional property `spec/dataSource/dataImport` from the response with the `202` status
  - removed the optional property `spec/engine/crVersion` from the response with the `200` status
  - removed the optional property `spec/engine/crVersion` from the response with the `201` status
  - removed the optional property `spec/engine/crVersion` from the response with the `202` status
  - removed the optional property `spec/engine/resources/limits` from the response with the `200` status
  - removed the optional property `spec/engine/resources/limits` from the response with the `201` status
  - removed the optional property `spec/engine/resources/limits` from the response with the `202` status
  - removed the optional property `spec/engine/resources/requests` from the response with the `200` status
  - removed the optional property `spec/engine/resources/requests` from the response with the `201` status
  - removed the optional property `spec/engine/resources/requests` from the response with the `202` status
  - removed the optional property `spec/engineFeatures` from the response with the `200` status
  - removed the optional property `spec/engineFeatures` from the response with the `201` status
  - removed the optional property `spec/engineFeatures` from the response with the `202` status
  - removed the optional property `spec/monitoring/resources/claims/items/request` from the response with the `200` status
  - removed the optional property `spec/monitoring/resources/claims/items/request` from the response with the `201` status
  - …58 more

---

[Operation](https://skmtc.dev/openeverest/apis/openeverest-schema/docs/namespaces/:namespace/database-clusters/post.md) - [API](https://skmtc.dev/openeverest/apis/openeverest-schema.md) - [Page](https://skmtc.dev/openeverest/apis/openeverest-schema/changes/namespaces/:namespace/database-clusters/post)
