You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d137594
Browse filesBrowse the repository at this point in the historyBrowse files
Support in-place update for service gateway (#4221)
The `gateway` property in service configurations
can now be updated in-place.
```shell
$ dstack apply -f my-service.dstack.yml
Active run my-service already exists. Detected changes that can be updated in-place:
- Configuration properties:
- gateway
Update the run? [y/n]: y
NAME BACKEND GPU PRICE STATUS SUBMITTED
my-service aws (us-east-2) - $0.0005 (spot) running 09:22
my-service provisioning completed (running)
Service is published at:
http://my-service.second-gateway.example.com
```
This allows you to reassign a service to a
different gateway without stopping the service.
```shell
$ dstack event
[2026-08-27 09:28:33] [run my-service, gateway second-gateway] Service assigned to gateway
[2026-08-27 09:28:33] [👤admin] [run my-service] Run updated. Deployment: 1. Changed fields: configuration.gateway
[2026-08-27 09:28:39] [run my-service, gateway-replica first-gateway-0] Service unregistered
[2026-08-27 09:28:39] [job my-service-0-0, gateway-replica first-gateway-0] Service replica unregistered
[2026-08-27 09:28:41] [run my-service, gateway-replica second-gateway-0] Service registered
[2026-08-27 09:28:41] [job my-service-0-0, gateway-replica second-gateway-0] Service replica registered
```
Migrating between gateways would typically result
in service downtime while you are rerouting your
client traffic to the new gateway. During
reassignment, the service may also be unavailable
on both gateways for a brief period (several
seconds).
Migration from a gateway to running without a
gateway (`gateway: false`) and vice versa is also
supported.
Copy file name to clipboardExpand all lines: mkdocs/docs/concepts/services.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1534,7 +1534,7 @@ The rolling deployment stops when all replicas are updated or when a new deploym
1534
1534
1535
1535
Rolling deployment supports changes to the following properties: `port`, `probes`, `resources`, `volumes`, `docker`, `files`, `image`, `user`, `privileged`, `entrypoint`, `working_dir`, `python`, `nvcc`, `single_branch`, `env`, `shell`, `commands`, as well as changes to [repo](#repos) or [file](#files) contents.
1536
1536
1537
-
Changes to `replicas`and `scaling` can be applied without redeploying replicas.
1537
+
Changes to `priority`, `replicas`, `scaling`, and `gateway` can be applied without redeploying replicas.
1538
1538
1539
1539
Changes to other properties require a full service restart.
0 commit comments