Skip to content

[Feature]: Respect nodes.target during fleet in-place update #3812

Closed as not planned

Description

@jvstme

Problem

nodes.target is ignored when performing fleet in-place update. Respecting nodes.target will allow to:

  • Pre-provision more instances into an existing fleet.
  • Terminate excessive idle fleet instances.

Solution

Respect nodes.target during fleet in-place update.

  • If nodes.target is greater than the current number of instances, provision new ones to reach nodes.target.
  • If nodes.target is less than the current number of instances, terminate some of the idle ones to get as close as possible to nodes.target. Do not terminate busy instances.
  • If nodes.target is equal to the current number of instances or unspecified, do nothing.

Workaround

  • For pre-provisioning ­— increase nodes.min, apply, revert nodes.min, apply.
  • For terminating — dstack fleet delete -i ...

Would you like to help us implement this feature by sending a PR?

Yes

Activity

  1. jvstme commented on Apr 22, 2026

    @jvstme
    CollaboratorAuthor

    @r4victor, does this match what you have in mind for fleet in-place update?

  2. r4victor commented on Apr 23, 2026

    @r4victor
    Collaborator

    Yes, I was thinking about it when doing #3775 but decided to do it separately since " terminate some of the idle ones" will require locking instances in fleet apply, which is not currently necessary for other in-place updates.

  3. github-actions commented on May 24, 2026

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  4. github-actions commented on Jun 7, 2026

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions