🌱Bump to k8s.io/* v0.34.0-alpha.1

[dongjiang1989]

Bump the k8s.io/* deps to the latest tag

[k8s-ci-robot]

Hi @dongjiang1989. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[sbueringer]

/ok-to-test

@dongjiang1989 Thx for the PR, if there is no need to bump to alpha.1 at this time. I would probably defer merging this until later until we have a beta.

As soon as we merge this we would have to branch away to create v0.18.x patch release. I would like to avoid this if there is no need to pick up the alpha of v0.34 already.

In any case it's good to see if CI is still green and we can continue to bump k8s.io on this PR to run tests

[dongjiang1989]

@dongjiang1989 Thx for the PR, if there is no need to bump to alpha.1 at this time. I would probably defer merging this until later until we have a beta.

Thanks @sbueringer
I got it
Fix unittest case

[sbueringer]

cc @alvaroaleman (in case you want to bump to alpha.1 now somehow in the context of the ongoing SSA work)

[alvaroaleman]

cc @alvaroaleman (in case you want to bump to alpha.1 now somehow in the context of the ongoing SSA work)

No, the changes I would need aren't in alpha.1, but probably good to use the latest version regardless

[sbueringer]

cc @alvaroaleman (in case you want to bump to alpha.1 now somehow in the context of the ongoing SSA work)

No, the changes I would need aren't in alpha.1, but probably good to use the latest version regardless

I'm also fine with bumping. Just have to keep in mind that we should create a release branch based on a commit before this PR + start cherry-picking if we want to do patch releases of v0.18.0

(just mentioning it because in CT we often released patches from main, but not a big deal)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dongjiang1989
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sbueringer]

@dongjiang1989 Please rebase onto main & squash (to remove the merge commit)

[k8s-ci-robot]

@dongjiang1989: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-controller-tools-test-main	a400736	link	true	/test pull-controller-tools-test-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

[sbueringer]

@dongjiang1989 Please rebase onto main & squash (to remove the merge commit)

+ let's bump to alpha 2 directly

[dongjiang1989]

@dongjiang1989 Please rebase onto main & squash (to remove the merge commit)

• let's bump to alpha 2 directly

Thanks @sbueringer

add PR #1225

I'll close this PR