-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Make alternative container runtimes easier to use #8700
Milestone
Comments
This was referenced Oct 31, 2023
Merged
Reopening as incomplete. Unfortunately the linked PR used the "fixes" keyword which causes auto-closing of issues. |
This was referenced Dec 8, 2023
This was referenced Dec 8, 2023
Validated on Version:-$ k3s version v1.28.4+k3s-71a3c35f (71a3c35f)
Environment DetailsInfrastructure Node(s) CPU architecture, OS, and Version: Cluster Configuration: Steps to validate the fix
Reproduction Issue:
Validation Results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should:
RuntimeClass
resources for any runtimes that we support auto-detecting. These are cluster-level resources, and it is harmless for these to be present even if some/all nodes do not have the matching runtime in their containerd config.containerd.config.toml
. Users frequently make mistakes and open issues when this breaks, as it not trivial to do correctly.nvidia
andnvidia-experimental
. The checks are trivial (searching for binaries in a couple paths) and should be easy to extend.The text was updated successfully, but these errors were encountered: