Skip to content

[Docs] Clarify how K8s resources and offers work #3565

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
un-def merged 2 commits into from
Feb 20, 2026
Merged

[Docs] Clarify how K8s resources and offers work #3565

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8923b73
[Docs] Clarify how K8s resources and offers work
un-def Feb 11, 2026
8aad4ef
[Docs] Minor update to the `Resources and offers` under `Kubernetes` …
peterschmidt85 Feb 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 37 additions & 1 deletion docs/docs/concepts/backends.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1060,7 +1060,43 @@ projects:

Ensure you've created a ClusterRoleBinding to grant the role to the user or the service account you're using.

> To learn more, see the [Lambda](../../examples/clusters/lambda/#kubernetes) and [Lambda](../../examples/clusters/crusoe/#kubernetes) examples.
??? info "Resources and offers"
If you use ranges with [`resources`](../concepts/tasks.md#resources) (e.g. `gpu: 1..8` or `memory: 64GB..`) in fleet or run configurations, other backends collect and try all offers that satisfy the range.

The `kubernetes` backend handles it differently.

* For `gpu`, if you specify a range (e.g. `gpu: 4..8`), the `kubernetes` backend only provisions pods with the GPU count equal to the lower limit (`4`). The upper limit of the GPU range is always ignored.
* For other resources such as `cpu`, `memory`, and `disk`, the `kubernetes` backend passes the lower and upper limits of the range as Kubernetes [requests and limits](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits) respectively. If the upper limit is not set, the Kubernetes limit is also not set.

Example:

<div editor-title=".dstack.yml">

```yaml
type: dev-environment
ide: vscode

resources:
cpu: 32..64
memory: 1024GB
disk: 100GB..
gpu: nvidia:4..8
```

</div>

This translates to the following Kubernetes resource spec:

| Resource | Request | Limit |
|---------------------|----------|-----------|
| `cpu` | `32` | `64` |
| `memory` | `1024Gi` | `1024Gi` |
| `ephemeral-storage` | `100Gi` | _not set_ |
| `nvidia.com/gpu` | `4` | `4` |

This applies to offers shown in `dstack apply` (run plans), during provisioning, and in `dstack offer`. Unlike other backends, offers for the `kubernetes` backend always reflect the lower limit of the range.

> To learn more, see the [Lambda](../../examples/clusters/lambda/#kubernetes) and [Crusoe](../../examples/clusters/crusoe/#kubernetes) examples.

### RunPod

Expand Down