good first issuehelp wantedkind/feature
仓库指标
- 星标
- (10,380 个星标)
- PR 合并指标
- (平均合并 25天) (30 天内合并 26 个 PR)
描述
What would you like to be added
We currently use (AFAICT):
- ctr
- crictl
- nerdctl
If possible, we should use only one CRI frontend for manipulating images and containers.
Why is this needed
- Avoiding complexity in the playbooks and roles (usage of "command variables" such as
crictl_image_pull_command, etc) - Reducing the number of tasks, download and config steps.
Not sure what the pros and cons of each are. ctr looks more minimal, maybe that's enough for what we need to do in Kubespray ? wdyt @yankay @mzaian @floryut @MrFreezeex ?
EDIT: We'll use crictl as it's required by kubeadm, and compatible with all container runtime. -> this is no longer the case.
Usage sites can be converted by small batch, then once the conversion is done we'll be able to remove the download of nerdctl and ctr.
Blockers: mainly the usage of save/load, as this isn't in CRI.