Control versions of CRI and CNI installed in KIC

[afbjorklund]

Currently installing random versions from the cri-o repository:

containernetworking-plugins cri-tools

docker@minikube:~$ sudo crictl --version
crictl version v1.21.0
docker@minikube:~$ sudo /opt/cni/bin/portmap --version
CNI portmap plugin version unknown

cri-tools/now 1.21.0~2 amd64 [installed,local]
containernetworking-plugins/now 100:1.1.1~1 amd64 [installed,local]

https://build.opensuse.org/project/show/devel:kubic:libcontainers:stable

These should be matched, with what Kubernetes (kubeadm) requires:

cri-tools/kubernetes-xenial,now 1.25.0-00 amd64 [installed]
kubernetes-cni/kubernetes-xenial,now 1.1.1-00 amd64 [installed]

https://apt.kubernetes.io (repackaged, from the original github binaries)

---

Also needs to be decoupled from the container runtime installation.

So that you can install only docker or only containerd, without cri-o:

• Separate container runtimes from the image #9989

Therefore it would be better to not install them from the Kubic repository.

[afbjorklund]

These are the versions used by Kubernetes packages:

%global CRI_TOOLS_VERSION 1.24.2
%global CNI_VERSION 0.8.7

https://github.com/kubernetes/release/blob/master/packages/rpm/kubelet.spec

---

These are the versions used by kind, for the "base" image:

ARG CRICTL_VERSION="v1.24.0"
ARG CNI_PLUGINS_VERSION="v1.1.1"

https://github.com/kubernetes-sigs/kind/blob/main/images/base/Dockerfile

[afbjorklund]

Versions used for ISO image:

• Upgrade cri-tools from 1.21.0 to 1.24.2 #14831
• Upgrade cni-plugins from 0.8.5 to 0.8.7 #14829

Installed from upstream binaries.

• https://github.com/kubernetes-sigs/cri-tools
• https://github.com/containernetworking/plugins

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

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, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[afbjorklund]

Needs to be bumped:

• cri-tools 1.25.0
• cni-plugins 1.1.1

CRICTL_VERSION="v1.25.0"
CNI_PLUGINS_VERSION="v1.1.1"

[afbjorklund]

/remove-lifecycle stale

[afbjorklund]

Should just remove the package installation, and install from tarballs (like with containerd/buildkit)

Unfortunately this also means installing the systemd files manually, instead of just using a package.