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
We would like eksctl to enable support for launching Managed and Unmanaged Nodes for AWS Neuron instance types (Inferentia and Trainium Instances) with Bottlerocket AMIs. This includes launching the neuron-device-plugin.
The standard Bottlerocket AMI variant (aws-k8s-1.xx) from v1.27.0 onwards has this support built in. The upcoming AMI will have greater support as described below.
For a Proof Of Concept and local testing, the following diff was used:
Bottlerocket OS is adding support for Neuron Instances. At this time, the OS already ships with the Neuron device drivers and can use the Neuron device. With the new setting change linked, containers should be able to take ownership of requested devices.
The text was updated successfully, but these errors were encountered:
Hello vigh-m 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website
What feature/behavior/change do you want?
We would like eksctl to enable support for launching Managed and Unmanaged Nodes for AWS Neuron instance types (Inferentia and Trainium Instances) with Bottlerocket AMIs. This includes launching the
neuron-device-plugin
.The standard Bottlerocket AMI variant (
aws-k8s-1.xx
) fromv1.27.0
onwards has this support built in. The upcoming AMI will have greater support as described below.For a Proof Of Concept and local testing, the following diff was used:
Why do you want this feature?
Bottlerocket OS is adding support for Neuron Instances. At this time, the OS already ships with the Neuron device drivers and can use the Neuron device. With the new setting change linked, containers should be able to take ownership of requested devices.
The text was updated successfully, but these errors were encountered: