Update PPC UT-job configs for releases 1.33, 1.34, 1.35
This PR adds PPC unit test jobs for k8s releases 1.33, 1.34, and 1.35 and sets up automation for future release branch job creation.
- Added K8s unit test jobs for the 1.35 branch for the ppc64le provider.
- Updated jobs for releases 1.33 and 1.34 to ensure consistency.
- Added
fork-per-releaseandfork-per-release-cronannotations. - Configured jobs to be automatically generated for future releases using
config-forkerandconfig-rotatorif needed.
Hi @varshadeshmane92. Thanks for your PR.
I'm waiting for a github.com 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.
/cc @Rajalakshmi-Girish
/test all
/lgtm /approve
Please create a release job for every supported branch. As of this message, 1.32 is supported, but it will be EoL in just over 2 months. The good news is that your job gets added to a shared file that will be dropped by sig-release at the end of the support window, along with everyone else's 1.32 jobs.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Rajalakshmi-Girish, varshadeshmane92 Once this PR has been reviewed and has the lgtm label, please ask for approval from xmudrii. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
- ~~config/jobs/kubernetes/cloud-provider-ibmcloud/OWNERS~~ [Rajalakshmi-Girish]
- config/jobs/kubernetes/sig-release/OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@xmudrii The changes required for adding jobs for all the supported release branches(1.35, 1.34, 1.33) is made. I also had a query regarding these annotations in other similar jobs..I posted here https://kubernetes.slack.com/archives/C2C40FMNF/p1766492686545179
@varshadeshmane92 ^^