Open xmudrii opened 1 year ago
Relevant to #3055
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
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
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
cri-tools referencing issue: https://github.com/kubernetes-sigs/cri-tools/issues/1248
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
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
andkrel 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