kubernetes-sigs/cluster-api

:book: Add documentation on effective use of failure domains

Open

#5,542 opened on Oct 29, 2021

View on GitHub
 (8 comments) (0 reactions) (0 assignees)Go (1,532 forks)auto 404
help wantedkind/documentationpriority/backlogtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

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

Contributor guide

Research direction
Investigate how MachineDeployments (single failure domain) and MachinePools (multiple failure domains) handle failure domains/AZs in Cluster API. Review existing code and documentation, then write a guide on best practices for scaling across availability zones considering data locality and high availability.
Tech stack
go
Domain
devopsinfrastructure
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Kubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75