0.17.0

Service auto-scaling

Previously, dstack always served services as single replicas. While this is suitable for development, in production, the service must automatically scale based on the load.

That's why in 0.17.0, we extended dstack with the capability to configure replicas (the number of replicas) as well as scaling (the auto-scaling policy).

Regions and instance types

The update brings support for specifying regions and instance types (in dstack run and .dstack/profiles.yml)

Environment variables

Firstly, it's now possible to configure an environment variable in the configuration without hardcoding its value. Secondly, dstack run now inherits environment variables from the current process.

For more details on these new features, check the changelog.

What's changed

• Support running multiple replicas for a service by @Egor-S in #986 and #1015
• Allow to specify instance_type via CLI and profiles by @r4victor in #1023
• Allow to specify regions via CLI and profiles by @r4victor in #947
• Allow specifying required env variables by @spott in #1003
• Allow configuring CA for gateways by @jvstme in #1022
• Support Python 3.12 by @peterschmidt85 in #1031
• The shm_size property in resources doesn't take effect by @peterschmidt85 in #1007
• Sometimes, runs get stuck at pulling by @TheBits in #1035
• vastai doesn't show any offers since 0.16.0 by @iRohith in #959
• It's not possible to configure projects other than main by @peterschmidt85 in #992
• Spot instances don't work on GCP by @peterschmidt85 in #996

New contributors

• @iRohith made their first contribution in #959
• @Bihan made their first contribution in #928

Full changelog: 0.16.5...0.17.0