-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add nerdctl to kind #2517
Comments
/cc @aojea |
per the comment
doesn't seem KIND needs to add anything |
Yes, it is actualy saying use BTW, what do u think about add |
this is perhaps a bit clearer, but essentially a dupe of #2317? |
We already provide ctr (which we currently use internally) and crictl (which is a standard tool portable across kubernetes clusters), which add a fair bit to the image size. As big as the images are we do everything we can to keep them lighter. User workloads really shouldn't be talking to the node runtime directly. You should use the Kubernetes APIs .. 🤔 |
Thanks for reply! I was trying to lean how node runtime works in KIND and i found that nerdctl is more easy to use(for me). So I guess someone should have the same needs as me. It is ok if we don't add it to the base image for keep it lighter.Just a suggestion 😄 |
I think probably we should be considering adding support for nerdctl/lima (especially if someone wants to outline the approach and take it on themselves), but currently even the podman support is a bit lacking (see e.g. #2038). Within the nodes I think we should not add this additional tool, preferring the Kubernetes API instead (and we do also provide |
What would you like to be added:
Add nerdctl to kind because it is very friendly to people who are familiar with docker-cli rather than ctr.
Why is this needed:
And add
nerdctl
to kind will make it more easy to use on testing purposes.The text was updated successfully, but these errors were encountered: