Make release with latest translation-lib

[mattcary]

Should happen before 1.21 release.

kubernetes/kubernetes#97823 has the changes we want.

/cc @Jiawei0227

[pohly]

#564 should also be included in that release.

[mattcary]

Also the new migration metrics, kubernetes-csi/csi-lib-utils#77.

[chrigl]

kubernetes/kubernetes#98311 would be great as well. It is already on release-1.20 (not tagged yet) and tag v1.21.0-alpha.3.

[andyzhangx]

@msau42 @Jiawei0227 could you help release 2.1.1 version, it has one critical csi migration fix, thanks.

[Jiawei0227]

@andyzhangx I will create a release-note after #567 being merged tomorrow.

[pohly]

Can we also get #565 included?

[pohly]

It looks like v2.1.0 was tagged on master and all changes since then are bug fixes for a v2.1.1 release or build fixes that we need to test that release on Kubernetes 1.20:
v2.1.0...master

I would be okay to just tag v2.1.1 on master. We can also create a release-2.1 branch, it just would be identical to master for now.

[msau42]

I will create a release branch so that we're consistent in our release process. I think the release-notes tool doesn't support patch releases on master branch when using a discover method.

[msau42]

release-2.1 is created. I took everything up until (not including) #560 as that change potentially requires action from consumers of migrated plugins.

For any bug fixes after that release-2.1...master, please open a cherry-pick PR

[pohly]

Here's the one I care about: #568

[pohly]

I'm checking the release-2.1 branch.

Can we also get #565 included?

Done, through PR #568.

kubernetes/kubernetes#98311 would be great as well

That implies bumping k8s.io/csi-translation-lib to a version > v1.21.0-alpha.3. I don't think we should be doing that in a release branch, but I am not sure. @msau42, @jsafrane, what do you think?

Also the new migration metrics, kubernetes-csi/csi-lib-utils#77.

Should not be included according to @msau42 ("that change potentially requires action from consumers of migrated plugins").

As it looks like we don't have other pending fixes, I went ahead and prepared release notes:
#578

[msau42]

I think we should update csi-translation-lib in the patch release. It contains a number of fixes for many plugins. @Jiawei0227 can you help with that?

[ialidzhikov]

I think this issue can be closed as new releases that vendor the latest csi-translation-lib were cut - v2.1.1, v2.2.0.

[pohly]

/close

[k8s-ci-robot]

@pohly: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pohly]

/reopen

#621 is still pending?

[k8s-ci-robot]

@pohly: Reopened this issue.

In response to this:

/reopen

#621 is still pending?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[Jiawei0227]

/close