:book: Add documentation on effective use of failure domains

[randomvariable]

User Story

As an operator, I see that MachineDeployments only support a single failure domain / AZ, and MachinePools support multiple. I need some guidance on how to effectively scale and distribute across AZs in respect of availability and data locality requirements

Detailed Description

[A clear and concise description of what you want to happen.]

Anything else you would like to add:

[Miscellaneous information that will assist in solving the issue.]

/kind feature

cc @dthorsen

[fabriziopandini]

Ideally, also KCP support for failure domains should be documented

/remove-kind feature
/kind documentation
/milestone v1.1

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[fabriziopandini]

/remove-lifecycle stale

[vincepri]

/milestone Next
/lifecycle frozen