Update PPC UT-job configs for releases 1.33, 1.34, 1.35

[varshadeshmane92]

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-release and fork-per-release-cron annotations.
• Configured jobs to be automatically generated for future releases using config-forker and config-rotator if needed.

[k8s-ci-robot]

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.

Details

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.

[kishen-v]

/cc @Rajalakshmi-Girish

[Rajalakshmi-Girish]

/lgtm

[Rajalakshmi-Girish]

/test all

[Rajalakshmi-Girish]

/lgtm
/approve

[Rajalakshmi-Girish]

@upodroid Your opinion on this please?

[upodroid]

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.

[Rajalakshmi-Girish]

@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 ^^

[Rajalakshmi-Girish]

/ok-to-test

[xmudrii]

/lgtm
/approve
/hold
We're close to the patch releases, let's merge this after patch releases for January are out

[xmudrii]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Rajalakshmi-Girish, varshadeshmane92, xmudrii

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/cloud-provider-ibmcloud/OWNERS [Rajalakshmi-Girish]
• config/jobs/kubernetes/sig-release/OWNERS [xmudrii]

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

[xmudrii]

/hold cancel

[xmudrii]

This PR is not actually adding tests to informing/blocking dashboards, so this should be safe to merge.

[k8s-ci-robot]

@varshadeshmane92: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key cloud-provider-ibmcloud-ppc64le-periodics.yaml using file config/jobs/kubernetes/cloud-provider-ibmcloud/cloud-provider-ibmcloud-ppc64le-periodics.yaml
• key 1.32.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.32.yaml
• key 1.33.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.33.yaml
• key 1.34.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.34.yaml
• key 1.35.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.35.yaml

Details

In response to this:

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-release and fork-per-release-cron annotations.
• Configured jobs to be automatically generated for future releases using config-forker and config-rotator if needed.

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.