cri-tools icon indicating copy to clipboard operation
cri-tools copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Update Readme to reflect new way of obtaining deb/rpm packages

Open dionysius opened this issue 7 months ago • 3 comments
trafficstars

What happened:

Followup for https://github.com/kubernetes-sigs/cri-tools/issues/1244. It is time to reflect the correct repo/link in the Readme in some way.

What you expected to happen:

The Readme doesn't send me to outdated and unmaintained repositories.

Anything else we need to know?:

Quickly checked that cri-tools as a package indeed exists there

dionysius avatar Mar 27 '25 17:03 dionysius

Thank you for the suggestion @dionysius! Do you think that you'd like to contribute that change?

saschagrunert avatar Mar 28 '25 07:03 saschagrunert

There doesn't exist a good place to link to reliably longterm

  • https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/ is a "blog post"
  • https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-using-native-package-management is only for kubectl
  • https://kubernetes.io/docs/reference/tools/ doesn't offer/explain installation

Needs to be escalated to documentation

dionysius avatar Mar 31 '25 08:03 dionysius

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

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

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

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

/lifecycle stale

k8s-triage-robot avatar Jun 29 '25 09:06 k8s-triage-robot

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

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

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

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

/lifecycle rotten

k8s-triage-robot avatar Jul 29 '25 10:07 k8s-triage-robot

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

k8s-triage-robot avatar Aug 28 '25 10:08 k8s-triage-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-sigs/prow repository.

k8s-ci-robot avatar Aug 28 '25 10:08 k8s-ci-robot

/reopen /remove-lifecycle rotten

the deb/rpm link is still incorrect. Should we just drop it?

/help

SergeyKanzhelev avatar Sep 02 '25 16:09 SergeyKanzhelev

@SergeyKanzhelev: Reopened this issue.

In response to this:

/reopen /remove-lifecycle rotten

the deb/rpm link is still incorrect. Should we just drop it?

/help

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.

k8s-ci-robot avatar Sep 02 '25 16:09 k8s-ci-robot

/kind documentation /remove-kind bug

SergeyKanzhelev avatar Sep 02 '25 16:09 SergeyKanzhelev

the deb/rpm link is still incorrect. Should we just drop it?

The trend seems to be to drop the deb/rpm packages altogether...

It is no longer needed to install crictl, when running kubeadm

So now both "crictl" and "critest" are development and debugging tools, and not required by kubeadm/kubelet/kubectl:

https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/ (only uses the tarballs)

That probably means that they will no longer be repackaged by OBS, similar to the proposed change for kubernetes-cni:

  • https://github.com/kubernetes/release/issues/4156

afbjorklund avatar Oct 12 '25 15:10 afbjorklund

Note that for the existing releases, there is no need to set up another repository since both cri-tools and kubernetes-cni are still in the "core" repo...

They are also still added as dependencies, so you get them installed whether you like it or not... But no instructions are needed, beyond setting up the OBS repo for your branch.

https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/

afbjorklund avatar Oct 13 '25 06:10 afbjorklund