Install cri-tools/cni-plugins with bootstrapper, and not with provisioner

[afbjorklund]

Currently, cri-tools and cni-plugins are installed together with the container runtime and re-used for all k8s versions.

But they are supposed to be installed together with the kubernetes installation, which could require specific versions.

Actually it is only crictl (not critest), and the flannel plugin has been scoped out (installed from external project)

The versions to use are included with the rpm/deb packaging, and mentioned in the documentation for the binaries:

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl

CRICTL_VERSION="v1.25.0"
https://github.com/kubernetes-sigs/cri-tools

CNI_PLUGINS_VERSION="v1.1.1"
https://github.com/containernetworking/plugins

The packages from kubernetes are just re-packaged from the binaries that are available on dl.k8s.io and github.com

---

Hopefully this feature will make it easier to keep them up-to-date, since they are now hopelessly out of date:

• Control versions of CRI and CNI installed in KIC #14830

The configuration of CRI and CNI is still needed, only the binaries are included in the upstream packaging.

They should probably just overwrite any existing /usr/bin/crictl and /opt/cni/bin, during the installation ?

[afbjorklund]

The v0.8.6 /opt/cni/bin/flannel installation, has been moved to an init container overwriting host...

So it is no longer provided by cni-plugins, but separately from: https://github.com/flannel-io/cni-plugin

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afbjorklund]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@afbjorklund: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[afbjorklund]

/reopen
/remove-lifecycle rotten

[k8s-ci-robot]

@afbjorklund: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.