Values.yaml uses external containerd to k3s

[ldabas-msft]

Shoudl the values.yaml not be using contaird managed by k3s internally, otherwise hwo does the cluster leverage nvdia?
Maybe this is a more appropriate implementation

toolkit:
env:
- name: CONTAINERD_CONFIG
value: "/var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl"
- name: CONTAINERD_SOCKET
value: "/run/k3s/containerd/containerd.sock"
- name: CONTAINERD_RUNTIME_CLASS
value: "nvidia"
- name: CONTAINERD_SET_AS_DEFAULT
value: "true"

devicePlugin:
config:
name: time-slicing-config-all
default: any

[UntouchedWagons]

The pod will use the nvidia runtime if it's specified in the manifest, see the nvidia-smi.yaml example.