cri-tools debs/rpms are not being published #739
Description
After taking a look at #737, I discovered a tangential problem, namely, we have not been publishing debs/rpms for cri-tools since v1.12.0:
debs
$ apt-cache show cri-tools
Package: cri-tools
Version: 1.12.0-00
Installed-Size: 27665
Maintainer: Kubernetes Authors <kubernetes-dev@googlegroups.com>
Architecture: amd64
Description: Container Runtime Interface Tools
Binaries that interact with the container runtime through the container runtime interface
Description-md5: c5a3d1c1edf49aa0775171c95e117e05
Homepage: https://kubernetes.io
Filename: pool/cri-tools_1.12.0-00_amd64_2d9f048a50a9dfeceebd84635f1322955aca6381d9c05b4d60b3da1edb7d856c.deb
Priority: optional
SHA256: 2d9f048a50a9dfeceebd84635f1322955aca6381d9c05b4d60b3da1edb7d856c
Section: misc
Size: 5342588
Package: cri-tools
Version: 1.11.1-00
Installed-Size: 27816
Maintainer: Kubernetes Authors <kubernetes-dev@googlegroups.com>
Architecture: amd64
Description: Container Runtime Interface Tools
Binaries that interact with the container runtime through the container runtime interface
Description-md5: c5a3d1c1edf49aa0775171c95e117e05
Homepage: https://kubernetes.io
Filename: pool/cri-tools_1.11.1-00_amd64_e6300f0f4ec2fb5d6967533416580e1a22be90277944370ceb2551b04d7bc1a3.deb
Priority: optional
SHA256: e6300f0f4ec2fb5d6967533416580e1a22be90277944370ceb2551b04d7bc1a3
Section: misc
Size: 5319986
Package: cri-tools
Version: 1.11.0-00
Installed-Size: 27712
Maintainer: Kubernetes Authors <kubernetes-dev@googlegroups.com>
Architecture: amd64
Description: Container Runtime Interface Tools
Binaries that interact with the container runtime through the container runtime interface
Description-md5: c5a3d1c1edf49aa0775171c95e117e05
Homepage: https://kubernetes.io
Filename: pool/cri-tools_1.11.0-00_amd64_768e5551f9badfde12b10c42c88afb45c412c1bf307a5985a4b29f4499d341bd.deb
Priority: optional
SHA256: 768e5551f9badfde12b10c42c88afb45c412c1bf307a5985a4b29f4499d341bd
Section: misc
Size: 5309448
Package: cri-tools
Version: 1.0.0-beta.1-00
Installed-Size: 26067
Maintainer: Kubernetes Authors <kubernetes-dev@googlegroups.com>
Architecture: amd64
Description: Container Runtime Interface Tools
Binaries that interact with the container runtime through the container runtime interface
Description-md5: c5a3d1c1edf49aa0775171c95e117e05
Homepage: https://kubernetes.io
Filename: pool/cri-tools_1.0.0-beta.1-00_amd64_68880f674e9bf5959744d2cde7389a1a57b857e3fb769051ae0c506b19269ff0.deb
Priority: optional
SHA256: 68880f674e9bf5959744d2cde7389a1a57b857e3fb769051ae0c506b19269ff0
Section: misc
Size: 5069050
rpms
# yum list cri-tools --show-duplicates
Loaded plugins: fastestmirror, ovl
Loading mirror speeds from cached hostfile
* base: ewr.edge.kernel.org
* extras: mirror.jaleco.com
* updates: mirror.jaleco.com
Available Packages
cri-tools.x86_64 1.0.0_beta.1-0 kubernetes
cri-tools.x86_64 1.11.0-0 kubernetes
cri-tools.x86_64 1.11.1-0 kubernetes
cri-tools.x86_64 1.12.0-0 kubernetes
Our current release tooling maps versions of cri-tools (>= 1.12.0) to the rest of the release packages.
This raises a set of questions...
- As we have not been publishing cri-tools debs/rpms, does that imply that release versions of cri-tools do not need to map (semver) to Kubernetes release semver? ref: Release and versioning kubernetes-sigs/cri-tools#297
- Who are the set of maintainers for cri-tools?
- What is the release process for cri-tools? Is there an order of operations i.e., does it need to be released before/after the corresponding Kubernetes version?
- Have we not been requesting cri-tools packages be pushed to the deb/rpm repos OR does the tooling we currently utilize not support that/has something changed in the tooling to prevent this (during, say, the post-1.12.0 timeframe)? ref: No xenial release available for 1.13 kubernetes-sigs/cri-tools#422
- How do we catch this in the future? k/k currently consumes the tarballs of cri-tools (Update cri-tools to v1.14.0 kubernetes#75658), so we're missing coverage here.