Skip to content

Conversation

@varshadeshmane92
Copy link

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 k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 16, 2025
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot added area/config Issues or PRs related to code in /config area/jobs labels Dec 16, 2025
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Dec 16, 2025
@kishen-v
Copy link
Contributor

/cc @Rajalakshmi-Girish

Copy link
Contributor

@Rajalakshmi-Girish Rajalakshmi-Girish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed lgtm "Looks good to me", indicates that a PR is ready to be merged. labels Dec 19, 2025
@varshadeshmane92 varshadeshmane92 force-pushed the update-ppc-ut-rel-branch-jobs branch from aefbbb6 to bd3a886 Compare December 19, 2025 09:18
@Rajalakshmi-Girish
Copy link
Contributor

/test all

@Rajalakshmi-Girish
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 19, 2025
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 19, 2025
Copy link
Contributor

@Rajalakshmi-Girish Rajalakshmi-Girish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@upodroid Your opinion on this please?

@upodroid
Copy link
Member

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.

@varshadeshmane92 varshadeshmane92 force-pushed the update-ppc-ut-rel-branch-jobs branch from bd3a886 to 03a6e85 Compare December 23, 2025 06:28
@k8s-ci-robot
Copy link
Contributor

[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.

Details Needs approval from an approver in each of these files:

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

@Rajalakshmi-Girish
Copy link
Contributor

Rajalakshmi-Girish commented Dec 23, 2025

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

@varshadeshmane92 varshadeshmane92 force-pushed the update-ppc-ut-rel-branch-jobs branch 2 times, most recently from e9b1e60 to 60eedb9 Compare December 29, 2025 04:14
@Rajalakshmi-Girish
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 29, 2025
@varshadeshmane92 varshadeshmane92 force-pushed the update-ppc-ut-rel-branch-jobs branch from 60eedb9 to 904bf24 Compare December 29, 2025 06:19
@varshadeshmane92 varshadeshmane92 force-pushed the update-ppc-ut-rel-branch-jobs branch from 904bf24 to 62d32a5 Compare December 29, 2025 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/config Issues or PRs related to code in /config area/jobs area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants