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
Ensure that the rke2-runtimeclasses chart is still in sync with all the supported runtime classes that are detected by k3s/rke2. In particular, I suspect that nvidia-smi may be missing.
Add that chart to RKE2.
Ensure that RKE2 assigns ownership of any supported RuntimeClass definitions to the rke2-runtimeclasses chart so that the helm install does not fail to install and go into crashloop backoff due to conflicting unmanaged resources. We should NOT take ownership of any runtimeclass definitions not managed by the chart, so that users can add their own.
For the final goal, this would probably look like a startup hook similar to https://github.com/rancher/rke2/blob/master/pkg/rke2/kp.go that iterates over the supported runtimeclass definitions and adds the correct helm labels/annotations.
The text was updated successfully, but these errors were encountered:
Follow up to:
We created a chart with RuntimeClass definitions, but never actually added it to RKE2:
We need to:
For the final goal, this would probably look like a startup hook similar to https://github.com/rancher/rke2/blob/master/pkg/rke2/kp.go that iterates over the supported runtimeclass definitions and adds the correct helm labels/annotations.
The text was updated successfully, but these errors were encountered: