release icon indicating copy to clipboard operation
release copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Automate building and publishing cri-tools and kubernetes-cni packages

Open xmudrii opened this issue 2 years ago • 12 comments

cri-tools and kubernetes-cni were automatically built and published on Google infra. However, as we don't have reproducible build (#3170), this is not an option on OBS. As of now, we can manually build and publish these packages using krel obs stage and krel obs release

While this is good enough for now, we should look into automating build and publish process for these packages. Automation can be based on some promotion workflow similar to images where you define in which project to build and publish these packages via some YAML manifest.

/sig release /area release-eng /kind feature /priority important-longterm

xmudrii avatar Jul 24 '23 20:07 xmudrii

Relevant to #3055

xmudrii avatar Jul 24 '23 20:07 xmudrii

Hi @xmudrii ,

I saw your LFX project about this issue , could please share the command line multiple steps you want to reduce by building a new library.

So that I can understand this project better as it's task are distributed among different issues

parteekcoder avatar Aug 07 '23 06:08 parteekcoder

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 Jan 25 '24 23:01 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jan 28 '24 20:01 xmudrii

The CNI plugins package is published in isv:kubernetes:core:shared right now. We manually aggregate them into the corresponding release project like this (for v1.30):

osc aggregatepac isv:kubernetes:core:shared/kubernetes-cni.20240110204507 isv:kubernetes:core:stable:v1.30:build
osc release isv:kubernetes:core:stable:v1.30:build/kubernetes-cni.20240110204507

saschagrunert avatar Apr 18 '24 09:04 saschagrunert

cri-tools referencing issue: https://github.com/kubernetes-sigs/cri-tools/issues/1248

saschagrunert avatar Apr 18 '24 09:04 saschagrunert

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 Jul 17 '24 09:07 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jul 23 '24 09:07 xmudrii