kubernetes-sigs / kubernetes-sigs/cluster-api

Support highly available CAPI management components across clusters.

Open
#7,459 6 comments 0 reactions 0 assignees View on GitHub
help wanted kind/feature kind/proposal priority/backlog triage/accepted
Dominant language
Go
Stars
4.3k
Forks
1.6k
Avg merge
1d 3h
Merged PRs (30d)
113

Description

**User Story**

As an operator I would like to be able to configure redundant Cluster API components across clusters for automatic failover of workload cluster management.

**Detailed Description**

In a failure scenario where a management cluster is not functioning or inaccessible, remediation is mostly manual. In production deployments that rely on CAPI to back a mid-tier for cluster lifecycle operations this could mean unacceptable downtime. I believe an active-passive configuration with automatic failover is more feasible in the short-term. An active-active configuration could help support load balancing efforts for environments with a higher number of cluster CRUD requirements.

**Anything else you would like to add:**

If the user story is achievable now this may just need documentation. Otherwise I suspect this functionality would require a larger KEP but I'm familiar with that process.

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

/kind feature

Contributor guide

Open the contributing guide

Research direction

Start with CONTRIBUTING.md and its CAEP process, then determine whether highly available CAPI management components across clusters are already supported. The issue provides no files or tests to inspect; completion would be either documentation of existing support or a larger proposal for active-passive or active-active failover.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.