kubernetes / kubernetes/release

Automatically promote cri-tools / cni plugins releases

Open
#2,693 25 comments 0 reactions 0 assignees View on GitHub
area/release-eng kind/feature lifecycle/frozen priority/important-soon sig/release
Dominant language
Go
Stars
504
Forks
556
Avg merge
18h 43m
Merged PRs (30d)
33

Description

We run the following manual promotion command for each release of the CNI plugins as well as cri-tools by using [kpromo](https://github.com/kubernetes-sigs/promo-tools/tree/main/cmd/kpromo):

```
> go install sigs.k8s.io/promo-tools/v3/cmd/kpromo@latest
> kpromo gh --org kubernetes-sigs --repo cri-tools --bucket k8s-artifacts-cri-tools --release-dir release --tags v1.25.0
```

or

```
> kpromo gh --org containernetworking --repo plugins --bucket k8s-artifacts-cni --release-dir release --tags v1.1.1
```

The question is, can we automate this away by using a periodic prow job?

Alternatives:
- Promote the artifacts directly via GitHub actions from the corresponding projects (requires auth to be setup correctly)
- Wait for https://github.com/kubernetes/sig-release/issues/1372

cc @kubernetes/release-managers

Contributor guide

Open the contributing guide

Research direction

Start by reading the kpromo gh command under promo-tools/cmd/kpromo and running the two documented promotion commands for cri-tools and CNI plugins. Determine how a periodic Prow job can invoke them and authenticate to the artifact buckets. Done means releases from both projects are promoted automatically without the current manual commands.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
ci-cd, devops, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.