Automate building and publishing cri-tools and kubernetes-cni packages #3171
Labels
area/release-eng
Issues or PRs related to the Release Engineering subproject
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
sig/release
Categorizes an issue or PR as relevant to SIG Release.
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
The text was updated successfully, but these errors were encountered: