NVIDIA Jetson GPU-Operator Support

[asierzd]

Hello,

I have been using a NVIDIA Jetson Orin Nano Developer Kit 8GB for running GPU workloads with Kubernetes, specifically with the K3s distribution, and using the NVIDIA k8s-device-plugin v0.17.1 without any issue (using the Helm chart installation, or with the manifest installation with kubectl).

I just had to install containerd in the Jetson, install and configure the nvidia-container-toolkit version 1.17.7-1 to use the containerd installed directly and CDI, and when deploying the K3s master node, specify the socket of containerd (with the --container-runtime-endpoint flag of K3s server CLI) in order to use our configured containerd as CRI with nvidia runtime, instead of using the default containerd that installs K3s.

I can give some more details of my Jetson setup, such as:

• K8s version: v1.31.5+k3s1
• Jetson Orin Nano DevKit with: JetPack 6.1, L4T 36.4.0

I hope it can be extended the GPU-Operator support for more NVIDIA GPUs, and more specifically for NVIDIA Jetson GPUs in the near future!

Thanks in advance!

[NoeSamaille]

Hi, I'm planning to do the same, any plans to have the NVIDIA Jetson Orin Nano Developer Kit 8GB supported by the GPU operator?

Thanks! :)

[NoeSamaille]

@asierzd Hi, can you share the GPU plugin device config you've used to get your Node to actually labelled properly? From some reason my Jetson Orin Nano Super Developer Kit 8GB doesn't get labelled ^^

[github-actions]

This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.

[francisguillier]

Hi,
I’ve added the request to our backlog, and we’ll prioritize it as we see increased demand.
Adding the label 'feature' to mark as RFE.

[francisguillier]

We’re closing this RFE for now, as Jetson support in the GPU Operator is not currently on our priority roadmap.

If this capability is critical to your environment, please feel free to reopen the issue and include the relevant use case and business justification so we can reassess its priority.