cri-tools debs/rpms are not being published #739

justaugustus · 2019-06-21T00:35:56Z

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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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.

The text was updated successfully, but these errors were encountered:

justaugustus · 2019-06-21T00:51:46Z

/cc @kubernetes/patch-release-team @kubernetes/release-managers @kubernetes/build-admins @kubernetes/sig-release-admins @feiskyer @Random-Liu

/priority critical-urgent
/milestone v1.16
/kind bug
/assign

justaugustus · 2019-06-21T01:14:59Z

/sig release
/area release-eng

BenTheElder · 2019-08-01T06:34:14Z

Who are the set of maintainers for cri-tools?

bump @Random-Liu

cpointner · 2019-10-29T17:08:06Z

Any news on this issue?

justaugustus · 2019-11-28T10:35:32Z

I'm working on a tool, kubepkg, which will make it easier to produce the packages. I'll continue work on this for 1.18.
/milestone v1.18

fejta-bot · 2020-02-26T11:17:07Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

cpointner · 2020-03-12T10:22:20Z

/remove-lifecycle stale

feiskyer · 2020-03-12T14:13:29Z

@justaugustus any progress on this?

saschagrunert · 2020-04-15T10:07:03Z

A quick summary from my side as discussed yesterday in the release engineering meeting:

We switched from release branches to master-based releases of cri-tools, which should theoretically allow us to use crictl v1.18.0 with Kubernetes v1.16.0 (just an example).
I had some issues in the past with some incompatibles between different gRPC versions (regarding dial context). I think we can explicitly mention that in the cri-tools release notes if that happens in the future.

This should be fine, right?

Some parts of the story are already done, should I take it over @justaugustus? (I think kubernetes/kubernetes#88408 needs to be fixed first, too)

saschagrunert · 2020-05-19T16:28:28Z

Probably related, we could publish the binary in the same way on the bucket to avoid "too many requests" failures when downloading from GitHub: kubernetes/kubernetes#91239

fejta-bot · 2020-08-17T16:52:16Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

saschagrunert · 2020-08-18T07:18:53Z

/remove-lifecycle stale

saschagrunert · 2020-09-24T20:27:11Z

I think this can be closed, right? We now manually update the releases by pushing the artifacts to GCS and then change it in k/k on our side.

saschagrunert · 2020-09-24T20:27:50Z

/close

Feel free to reopen if I miss anything.

k8s-ci-robot · 2020-09-24T20:28:04Z

@saschagrunert: Closing this issue.

In response to this:

/close

Feel free to reopen if I miss anything.

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.

paulcostinean · 2020-10-19T11:45:43Z

Can this be reopened?
Neither stable or unstable seem to include cri-tools past the 1.13 release.

k8s-ci-robot assigned justaugustus Jun 21, 2019

k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jun 21, 2019

k8s-ci-robot added this to the v1.16 milestone Jun 21, 2019

k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 21, 2019

This was referenced Jun 21, 2019

No xenial release available for 1.13 kubernetes-sigs/cri-tools#422

Closed

cri-tools was not upgraded to v1.14 in Kubernetes v1.15 #737

Closed

k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Jun 21, 2019

justaugustus mentioned this issue Jul 31, 2019

/build/dependencies.yaml should be in a sub-folder with multiple SIG owners kubernetes/kubernetes#80546

Closed

k8s-ci-robot modified the milestones: v1.16, v1.18 Nov 28, 2019

justaugustus mentioned this issue Jan 30, 2020

CNI plugins (kubernetes-cni) build and packaging process improvements kubernetes/sig-release#245

Open

11 tasks

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 26, 2020

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 12, 2020

saschagrunert mentioned this issue Apr 15, 2020

provide a brew package kubernetes-sigs/cri-tools#587

Closed

justaugustus mentioned this issue May 25, 2020

gh2gcs: Add go-based CLI for uploading GH releases to GCS #1311

Merged

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 17, 2020

k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 18, 2020

k8s-ci-robot closed this as completed Sep 24, 2020

paulcostinean mentioned this issue Oct 19, 2020

publish new rpm/deb releases kubernetes-sigs/cri-tools#672

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

cri-tools debs/rpms are not being published #739

cri-tools debs/rpms are not being published #739

justaugustus commented Jun 21, 2019 •

edited

Loading

justaugustus commented Jun 21, 2019

justaugustus commented Jun 21, 2019

BenTheElder commented Aug 1, 2019

cpointner commented Oct 29, 2019

justaugustus commented Nov 28, 2019

fejta-bot commented Feb 26, 2020

cpointner commented Mar 12, 2020

feiskyer commented Mar 12, 2020

saschagrunert commented Apr 15, 2020

saschagrunert commented May 19, 2020

fejta-bot commented Aug 17, 2020

saschagrunert commented Aug 18, 2020

saschagrunert commented Sep 24, 2020

saschagrunert commented Sep 24, 2020

k8s-ci-robot commented Sep 24, 2020

paulcostinean commented Oct 19, 2020

cri-tools debs/rpms are not being published #739

cri-tools debs/rpms are not being published #739

Comments

justaugustus commented Jun 21, 2019 • edited Loading

debs

rpms

justaugustus commented Jun 21, 2019

justaugustus commented Jun 21, 2019

BenTheElder commented Aug 1, 2019

cpointner commented Oct 29, 2019

justaugustus commented Nov 28, 2019

fejta-bot commented Feb 26, 2020

cpointner commented Mar 12, 2020

feiskyer commented Mar 12, 2020

saschagrunert commented Apr 15, 2020

saschagrunert commented May 19, 2020

fejta-bot commented Aug 17, 2020

saschagrunert commented Aug 18, 2020

saschagrunert commented Sep 24, 2020

saschagrunert commented Sep 24, 2020

k8s-ci-robot commented Sep 24, 2020

paulcostinean commented Oct 19, 2020

justaugustus commented Jun 21, 2019 •

edited

Loading