Added ppc64le support

[mgiessing]

What type of PR is this?

/kind feature

What this PR does / why we need it:
This PR adds support for ppc64le architecture. Therefore the relevant checksums have been added accordingly.
At the moment this does only work with container_manager set to docker as there is no ppc64le release for the default value containerd. Tested it on RHEL/CentOS.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Add ppc64le support

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ mgiessing (a1dd3fa)

[k8s-ci-robot]

Welcome @mgiessing!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mgiessing. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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/test-infra repository.

[oomichi]

Nice work, thanks for doing this.
Could you update Does this PR introduce a user-facing change?: for Add ppc64le support.

/ok-to-test
/lgtm

[floryut]

/release-note-edit Add ppc64le support

[floryut]

/release-note-edit Add ppc64le support

kubernetes/test-infra#23473 ~~nicely not working 🤷

[floryut]

@mgiessing Not sure how many people need this but thanks 🙇

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, mgiessing

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [floryut]

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

[mgiessing]

@floryut Probably not as many as for x86, but it definately helps 🙌
Thanks for reviewing & merging - if there are issues related to Kubespray on ppc64le arch feel free to @ me there!

[mgiessing]

@floryut Just for my understanding (and let me say I'm not very experienced with a "general" releasing process at all):
What does it take that this PR makes it into a release?

I thought all approved PRs will basically make it into the next release, but that seems not to be the case. I just found out v2.18.1 still supports only i386, x86 & arm which means ppc64le users need to work on the master/main branch and that can sometimes be troublesome.
Hope you can enlighten me here 😅 - Thanks!

[floryut]

@floryut Just for my understanding (and let me say I'm not very experienced with a "general" releasing process at all): What does it take that this PR makes it into a release?

I thought all approved PRs will basically make it into the next release, but that seems not to be the case. I just found out v2.18.1 still supports only i386, x86 & arm which means ppc64le users need to work on the master/main branch and that can sometimes be troublesome. Hope you can enlighten me here 😅 - Thanks!

@mgiessing You thought right, but 2.18.1 is a minor 2.18 release containing only backport PR from master branch (and mainly bug fixing, sometimes feature)
This will be release as part of 2.19.x though 👍

[mgiessing]

Okay got it - thanks for clarification!