[WIP] VEP-258: Support for ppc64le Arch

[pkenchap]

What this PR does / why we need it:

This PR establishes the PPC64LE architecture working group (wg-arch-ppc64le) to support ppc64le architecture in KubeVirt clusters. This is the initial step in organizing community efforts for ppc64le architecture support.

The PR includes:

• Creation of wg-arch-ppc64le directory with charter and OWNERS files
• Charter defining the scope, governance, and roles for the work group
• OWNERS file establishing initial maintainership

Which issue(s) this PR fixes:
Related to VEP-258 (currently under review in kubevirt/enhancements)

Special notes for your reviewer:

This PR supports VEP-258, which is currently under review for adding ppc64le architecture support to KubeVirt. This work group will coordinate:

• Build processes for ppc64le architecture
• CI infrastructure and test lanes for ppc64le
• Cross-architecture compatibility and testing
• Community collaboration on ppc64le-specific issues

Additional integration with sigs.yaml and other community infrastructure will be added in follow-up PRs.

Checklist

• Design: Enhancement proposal VEP-258 is under review in kubevirt/enhancements repository
• PR: The PR description is expressive enough and will help future contributors
• Code: Follows KubeVirt community organization patterns
• Upgrade: No upgrade impact - organizational structure only
• Testing: Not applicable - organizational structure change only
• Documentation: Work group charter and OWNERS documentation created
• Community: Will announce to kubevirt-dev after PR merge

Release note:

Created PPC64LE architecture working group (wg-arch-ppc64le) to coordinate ppc64le architecture support in KubeVirt in support of VEP-258.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jean-edouard for approval. 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:

• OWNERS

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

[kubevirt-bot]

Hi @pkenchap. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

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.

[kubevirt-bot]

The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubevirt org. You can then trigger verification by writing /verify-owners in a comment.

• pkenchap
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
  • wg-arch-ppc64le/OWNERS