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
/area runtime-proxy
/area koordlet
Duplicate with #1051.
Sorry. The current version of runtimeproxy does not support CRI v1 API (>= k8s 1.26.0). It will be fixed in the following versions.
There is an alternative of using NRI (Node Resource Interface), which allows k8s 1.26 while requiring containerd >= 1.7.0. Please see this link if you are interested.
This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:
After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, the issue is closed
You can:
Mark this issue or PR as fresh with /remove-lifecycle stale
Close this issue or PR with /close
Thank you for your contributions.
What happened:
kubelet启动失败:
CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/koord-runtimeproxy/runtimeproxy.sock
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): v1.26.2The text was updated successfully, but these errors were encountered: