Skip to content

Update QUICKSTART-EKS.md #4603

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

Open
romanchyla wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Update QUICKSTART-EKS.md #4603

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 8 additions & 2 deletions QUICKSTART-EKS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -385,7 +385,11 @@ Bottlerocket `v1.30.0+` supports Neuron Instance Types such as: `inf1`, `inf2`,
[settings.kubernetes]
device-ownership-from-security-context = true
```
This setting allows the container to take ownership of the mounted Neuron device based on the `runAsUser` and `runAsGroup` values provided in the spec.

If you are provisioning nodes via [EKS Auto Mode](https://docs.aws.amazon.com/eks/latest/userguide/automode.html) the setting above is applied automatically - when using
different provisioning mechanisms such as Karpenter or modified AMIs, we recommend you set [user-data](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html).

The following setting allows the container to take ownership of the mounted Neuron device 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/):

```yaml
Expand All @@ -404,8 +408,10 @@ spec:
- name: test
image: amazonlinux:2023
resources:
requests:
aws.amazon.com/neuroncore: "1"
limits:
aws.amazon.com/neuron: "1"
```

Along with the `device-ownership-from-secuirity-context` setting, you will need to deploy the [neuron-device-plugin](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/kubernetes-getting-started.html#neuron-device-plugin), and optionally, the [neuron-scheduler](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/kubernetes-getting-started.html#neuron-scheduler-extension).
Along with the `device-ownership-from-secuirity-context` setting, you will need to deploy the [neuron-device-plugin](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/kubernetes-getting-started.html#neuron-device-plugin) in order to make neuron devices available to the container, and optionally, the [neuron-scheduler](https://awsdocs-neuron.readthedocs-hosted.com/en/latest/containers/kubernetes-getting-started.html#neuron-scheduler-extension).