Kubespray for Raspberry Pi clusters

[b23prodtm]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
https://github.com/kubernetes-sigs/kubespray/blob/master/docs/arch.md
Which issue(s) this PR fixes:

Fixes #4294

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[k8s-ci-robot]

Welcome @b23prodtm!

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: b23prodtm
To complete the pull request process, please assign mattymo
You can assign the PR to them by writing /assign @mattymo in a comment when ready.

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

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

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[b23prodtm]

Just disable the RPI3 minimal requirements, it pretended to work on 3 but now it's too low for installing any new pods, I've once run up the dashboard. These were the legacy values :

# Minimal memory requirement in MB for safety checks
minimal_node_memory_mb: 462
minimal_master_memory_mb: 762

[hafe]

I don't understand this pr, seems to be random changes all over the code base.

[k8s-ci-robot]

@b23prodtm: PR needs rebase.

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.

[b23prodtm]

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;} Hi , Thank you for reporting any feedback. This pretends to run kubespray with raspberry pi clusters (not cloud or vagrant). It's not random changes but correctives that fixes bugs found around and rising errors on raspberry Pi 4 s. I think ther's lot of tuning in os based tests and code syntax checks that I cannot commit in for. So I d like to pass this PR to each other and pin out about what improvements can be made to allow use of ARM and raspberry Pi systems in kubespray. I know about microk8s already, a good alternative too.  Greetings De: notifications@github.comEnvoyé: 27 août 2020 19:17À: kubespray@noreply.github.comRépondre à: reply@reply.github.comCc: b23prodtm@users.sourceforge.net; mention@noreply.github.comObjet: Re: [kubernetes-sigs/kubespray] Kubespray for Raspberry Pi clusters (#5679) I don't understand this pr, seems to be random changes all over the code base. —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

[hafe]

@b23prodtm these are random changes all over the code base that does not respect reviewers!

[EppO]

This PR is too big and modifies too many different things at once. Please open a PR per topic you're trying to address to reduce the scope. Closing that one
/close

[k8s-ci-robot]

@EppO: Closed this PR.

In response to this:

This PR is too big and modifies too many different things at once. Please open a PR per topic you're trying to address to reduce the scope. Closing that one
/close

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.