-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Install cri-tools/cni-plugins with bootstrapper, and not with provisioner #15460
Comments
The v0.8.6 So it is no longer provided by cni-plugins, but separately from: https://github.com/flannel-io/cni-plugin |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
/reopen |
@afbjorklund: Reopened this issue. In response to this:
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. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
/reopen |
@afbjorklund: Reopened this issue. In response to this:
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. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
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
(notcritest
), and theflannel
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:
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 ?The text was updated successfully, but these errors were encountered: