-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Have cri-tools installed and configured #1486
Comments
+1 on this
It is hard to understand that EKS nodes by default have a non-working version of a non-standard tool but do not have the standard tool recommended by upstream. |
|
AL2023 is missing the cri-tools |
Opened a new tracking issue for AL2023: #2163 The package is not available in the distro repos at this time. |
What would you like to be added:
Install cri-tools and configure it with /etc/crictl.yaml.
Previously there was an issue that requested this (#797) but it was closed by a change that introduced nerdctl instead.
AFAICT amazon-linux does have a cri-tools package, so installing it should be trivial.
Why is this needed:
Crictl is the officially documented tooling for kubernetes to troubleshoot nodes: https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/
Nerdctl does not have a concept of pods, while crictl does. This allows continuing to use pod semantics when troubleshooting within on a node using crictl vs using nerdctl and figuring out which containers belong to which pod (not terribly difficult, but still an extra step).
Having nerdctl on the nodes is nice and I think it belongs with any containerd installation by default, but the nodes are k8s nodes, missing capabilities that crictl does add, which is pod-aware semantics during troubleshooting.
Additional notes:
nerdctl is not properly configured on a node,
nerdctl ps
doesn't list anything, you have to usenerdctl --namespace="k8s.io" ps
. I'll open a separate ticket to fix that as well, because on a k8s node one would expect nerdctl to default to the kubernetes pods namespace.The text was updated successfully, but these errors were encountered: