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

kubernetes / release

Release infrastructure for Kubernetes and related components

Apache License 2.0

480 stars 496 forks source link

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

Open xmudrii opened 11 months ago

xmudrii commented 11 months ago

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 commented 11 months ago

Relevant to #3055

parteekcoder commented 11 months ago

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

k8s-triage-robot commented 5 months ago

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

xmudrii commented 5 months ago

/remove-lifecycle stale

saschagrunert commented 2 months ago

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 commented 2 months ago

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