Release new v0.1.x and 0.29.x to pick CVEs and features

[mihivagyok]

#569
#573
#564
#568

I can help with testing or with additional PRs if necessary. Thanks!

Tasks

Beta Give feedback

No tasks being tracked yet.

Tasks

Beta Give feedback

1. creat tag v0.1.8
2. create tag v0.28.4
3. create tag v0.29.1
4. create branch release-0.30
5. create tag v0.30.0
6. create tag v0.30.1
7. create tag v0.30.2
8. promote images

Tasks

Beta Give feedback

No tasks being tracked yet.

[jkh52]

For release-0.1 let's block on #573 before tag v0.1.8

release-0.28 looks ok to tag v0.28.4

release-0.29 is ok to tag v0.29.1 but it will not include several changes that are only in master (plenty of test improvements, maintenance, but notably changing container images to nonroot variant). If we were to backport that feature, let's block on #568. @mihivagyok is that your expectation, that we will wait for v0.30.x?

[jkh52]

Tag v0.1.8 is created.

[mihivagyok]

Hi @jkh52 ! Thanks!

My expectation is that we can include the listed changes above in the next versions.
If I need to cherry-pick to release branches, I can create the PRs.

We will start using Kubernetes 1.30 soon, so my expectation is that there will a new release v0.30.x.

Thanks!
Adam

[jkh52]

We will start using Kubernetes 1.30 soon, so my expectation is that there will a new release v0.30.x.

Agreed, this repo should soon create release-0.30 branch (from master) and release a v0.30.0. Some process details are unclear: there is not yet a (non-alpha) client-go v0.30.0 tag.

If I need to cherry-pick to release branches, I can create the PRs.

If you feel something in master belongs in v0.29.x range, please open cherry pick PRs to release-0.29 branch. But, for example, the nonroot variant change seems unjustified to backport, since it may break some users.

[jkh52]

@mihivagyok I created tags: v0.28.4, v0.29.1, and v0.30.0.

v0.30.0 introduces your change #564

[mihivagyok]

Thank you very much @jkh52 !

[jkh52]

Sent kubernetes/k8s.io#6554 for image promotion.

[jkh52]

Recent batch of release overhead is finished. We can open new tracking issues as needed.

[mihivagyok]

Thank you very much!