Umbrella issue: Addition of prow jobs to run on ppc64le arch

[Rajalakshmi-Girish]

This issue is to cover all the prow jobs that would be added to run and test ppc64le architecture:

• Gain ppc64le support for kubekins-e2e-v2 which will be primarily used by jobs kubekins-e2e-v2 multiarch support for ppc64le #34416
• Unit Tests using make test Run k8s unit tests on ppc64le #34574
• Conformance Tests using kubetest2 tf Run conformance tests using kubetest2 against ci latest k8s on ppc64le #34623, Changed powervs-ssh-key value used by ibm conformance job #34626
• Run e2e-node tests using kubetest2 on IBM powervs- https://github.com/kubernetes/test-infra/pull/34645/files
• Presubmit job for ibm test-infra - Add presubmit job for ibm test-infra and move preset label to config file #34667
• ibm-powervs-alpha-enabled-default - Job to run alpha-enabled-default tests on IBM powervs #34686
• ibm-powervs-default - Job to run E2E default tests on IBM powervs #34719
• ibm-powervs-ubuntu-containerd ( we don't focus much on ubuntu)
• ibm-powervs + ibm cloud provider e2e (WIP, Using Capi cluster with ibm cloud provider ccm,)
• ibm-master-serial - Enable Job for serial e2e on IBM powervs #35024
• ibm-master-slow - Job to run E2e slow tests on IBM powervs #35020
• capibm-conformance-powervs (CAPI + IBM e2e running conformance test for both PowerVS and VSI)
• ibm-powervs-block-csi-driver-e2e (https://github.com/kubernetes-sigs/ibm-powervs-block-csi-driver)
• ibm-vpc-block-csi-driver-e2e (https://github.com/kubernetes-sigs/ibm-vpc-block-csi-driver)
  Ref: https://kubernetes.slack.com/archives/C09QZ4DQB/p1742225363263569?thread_ts=1742221592.280199&cid=C09QZ4DQB

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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.

[Rajalakshmi-Girish]

cc @mkumatag

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

[mkumatag]

/reopen

Reopening this as we are still working on this.

[k8s-ci-robot]

@mkumatag: Reopened this issue.

In response to this:

/reopen

Reopening this as we are still working on this.

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.