Elastic Deployment Release Notes

2025-11-03

[New Feature] When container reuse is enabled, you can control the scope of container reuse via the reuse_container_scope field.

2025-07-24

[New Feature] Support for mapping two ports to the public internet; in addition to the previously supported port 6006, port 6008 has been added. [New Feature] In addition to the API, support for managing the scheduling blacklist via the web interface has been added.

2025-06-06

[New Feature] Added an Elastic Deployment API that returns data such as the remaining duration of purchased time packages for a specified deployment.

2025-04-18

[New Feature] The API for stopping containers now includes the no_cache field, which allows you to choose whether or not to exclude the container from the cache pool after it is stopped.

2025-03-25

[New Feature] The API for setting a scheduling host blacklist now allows you to set an expiration time for the blacklist.

[New Feature] Added an API to retrieve the list of active scheduling host blacklists

2025-03-11

[Optimization] For the CUDA version field in deployment scheduling conditions, which previously only supported setting a left-side range (greater than or equal to), the functionality has been optimized to support setting both left and right-side ranges (greater than or equal to and less than or equal to).

2025-03-05

[New Feature] Support for specifying commands to be executed before stopping a container when creating a deployment. This feature is available in both the web interface and the API. For the API, see the cmd_before_shutdown field in the Create Deployment endpoint.

[New Feature] The API for retrieving the deployment list now supports filtering by name and status (all, in progress, and stopped statuses).

[New Feature] The web interface now displays elastic deployment time-based packages in a grid layout, optimized from the previous method that required clicking to view details to a grid display of unused time-based packages.

2025-02-12

[New Feature] The API for retrieving GPU inventory now includes additional filtering criteria

2025-01-23

[New Feature] API for retrieving the container list; the status field has been added, allowing you to filter containers by status.

2025-01-09

[New Feature] When performing rolling updates via the web interface for editing, deploying, and executing, you can now set a version. You can either specify a custom name or use the system’s default naming convention, making it easier to distinguish between different “batches” of containers created using different images, commands, and other configurations. Additionally, a new column displaying the version number will be added to the container list on the web interface, and the following field has been added to the developer API endpoints for retrieving container details and lists: version

2024-12-16

[New Feature] Support for scheduling across multiple regions has been added; however, containers in different regions will mount file storage from their respective regions. The API for creating deployments now includes the dc_list field, which is used to set the regions (data_center) where containers can be scheduled. The field region_sign, previously used to specify regions, remains available; if both fields are filled in, the value in dc_list takes precedence.

2024-10-28

[New Feature] Support for selecting whether to use the TCP or HTTP protocol for port mapping of a container’s external service port. The following field has been added to the deployment API: service_port_protocol

2024-10-08

[New Feature] When stopping a container in the web interface for an elastic deployment of the ReplicaSet type, an option is now available to choose whether to decrease the number of replicas by one while stopping the container. This feature was already supported in the previous API; this update adds support for it in the web interface.

[New Feature] The web interface and API for stopping containers now support executing user-defined shell commands before stopping the container. A new parameter has been added to the container stop API: cmd_before_shutdown. Note that if this command blocks, it will prevent the container from being stopped successfully.