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
Copy file name to clipboardexpand all lines: website/content/en/preview/concepts/nodeclasses.md
+14
Original file line number
Diff line number
Diff line change
@@ -1353,6 +1353,20 @@ cluster-name = 'cluster'
1353
1353
'memory.available' = '12%%'
1354
1354
```
1355
1355
1356
+
#### Device ownership in Bottlerocket
1357
+
1358
+
Bottlerocket `v1.30.0+` supports device ownership using the [security context](https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) provided in the Kubernetes specfile. To enable this, you will need the following user-data configurations:
1359
+
1360
+
```toml
1361
+
[settings]
1362
+
[settings.kubernetes]
1363
+
device-ownership-from-security-context = true
1364
+
```
1365
+
1366
+
This allows the container to take ownership of devices allocated to the pod via device-plugins based on the `runAsUser` and `runAsGroup` values provided in the spec. For more details on this, see the [Kubernetes documentation](https://kubernetes.io/blog/2021/11/09/non-root-containers-and-devices/)
1367
+
1368
+
This setting helps you enable Neuron workloads on Bottlerocket instances. See [Accelerators/GPU Resources]({{< ref "./scheduling#acceleratorsgpu-resources" >}}) for more details.
1369
+
1356
1370
### Windows2019/Windows2022
1357
1371
1358
1372
* Your UserData must be specified as PowerShell commands.
0 commit comments