Skip to content

Replica group spot_policy and reservation#3932

Merged
jvstme merged 2 commits into
masterfrom
issue_3929_replica_reservation_and_spot
Jun 9, 2026
Merged

Replica group spot_policy and reservation#3932
jvstme merged 2 commits into
masterfrom
issue_3929_replica_reservation_and_spot

Conversation

@jvstme

@jvstme jvstme commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

Allow to define spot_policy and reservation
per replica group in service configurations.

type: service
image: my-image
port: 80

replicas:
- name: baseline
  reservation: my-reservation
  count: 1
- name: overflow
  spot_policy: auto
  count: 0..3
  scaling:
    metric: rps
    target: 1

Closes #3929

Allow to define `spot_policy` and `reservation`
per replica group in service configurations.

```yaml
type: service
image: my-image
port: 80

replicas:
- name: baseline
  reservation: my-reservation
  count: 1
- name: overflow
  spot_policy: auto
  count: 0..3
  scaling:
    metric: rps
    target: 1
```
@jvstme jvstme requested a review from Bihan June 5, 2026 07:33

@Bihan Bihan left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this check, when reservation is set at the replica-group level, it is resolved into
job.job_spec.requirements.reservation, while profile.reservation remains None.

Rest is ready to merge.

@jvstme jvstme requested a review from Bihan June 9, 2026 12:51
@jvstme jvstme merged commit eeb07cd into master Jun 9, 2026
24 checks passed
@jvstme jvstme deleted the issue_3929_replica_reservation_and_spot branch June 9, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Support distributing service replicas across reserved and spot capacity

2 participants