chore: add upgrade job

[ricolin]

Relate-to: #1068
Relate-to: #1282

Depends-On: #1408
Depends-On: #1409

[mnaser]

@ricolin does it make sense to branch 2024.1 so we can make upgrade job from 2024.1 to main since thats a more supported upgrade route?

The other thing I wanted to bring up is what do you think of introducing a new upgrade pipeline, because if we run upgrade jobs on every commit, we doubled or CI time potentially (which is already kinda long tbh)...

[ricolin]

@ricolin does it make sense to branch 2024.1 so we can make upgrade job from 2024.1 to main since thats a more supported upgrade route?
I trust your experience with upgrade:) and avoid cross multi-version upgrade sounds like a good plan too.

The other thing I wanted to bring up is what do you think of introducing a new upgrade pipeline, because if we run upgrade jobs on every commit, we doubled or CI time potentially (which is already kinda long tbh)...

Agree, +1 on a upgrade pipeline with comment_filter so we can do verify when we plan to before release or make it a perodic job.

[mnaser]

I'm going to spend a bit of time thinking how we can accomplish this in a way where we have a separate pipeline probably or a periodic job.

[ricolin]

recheck

[ricolin]

/cherry-pick stable/2024.1

[vexxhost-bot]

@ricolin: once the present PR merges, I will cherry-pick it on top of stable/2024.1 in a new PR and assign it to you.

In response to this:

/cherry-pick stable/2024.1

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.

[ricolin]

/cherry-pick stable/2023.2

[vexxhost-bot]

@ricolin: once the present PR merges, I will cherry-pick it on top of stable/2023.2 in a new PR and assign it to you.

In response to this:

/cherry-pick stable/2023.2

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.

[ricolin]

/cherry-pick stable/2023.1

[vexxhost-bot]

@ricolin: once the present PR merges, I will cherry-pick it on top of stable/2023.1 in a new PR and assign it to you.

In response to this:

/cherry-pick stable/2023.1

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.

[vexxhost-bot]

@ricolin: new pull request created: #1519

In response to this:

/cherry-pick stable/2024.1

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.

[vexxhost-bot]

@ricolin: new pull request created: #1521

In response to this:

/cherry-pick stable/2023.2

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.

[vexxhost-bot]

@ricolin: new pull request created: #1522

In response to this:

/cherry-pick stable/2023.1

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.