kubernetes-retired/kubefed resource
Kubernetes Cluster Federation observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 8
- Longevity 100
Flags: archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3158
- days_rel: n/a
- days_push: 1258
- n_releases_24m: 0
Adoption not part of the score
2478 stars · 532 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Kubernetes Cluster Federation (KubeFed) enables coordinating configuration and workloads across multiple Kubernetes clusters from a single control plane. The repository has been archived and is no longer under active development.
Use cases
- manage multiple kubernetes clusters from one control plane
- federate deployments across clusters
- replicate kubernetes resources to many clusters
- multi-cluster dns and failover
- cross-cluster scheduling of workloads
When to choose
- you need to study the historical federation approach to multi-cluster kubernetes
- you already run kubefed and need to maintain an existing deployment
When to avoid
- starting a new multi-cluster project - the repo is archived
- you want actively maintained multi-cluster tooling - see current SIG Multicluster subprojects
Facets
infra-config · maturity abandoned
container-orchestration deployment configuration-management cloud-computing microservices go cloud kubernetes multi-cluster federation archived containers devops linux
1 source
- readme: https://github.com/kubernetes-retired/kubefed · fetched 2026-08-28 · c46b8996e618
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| kubernetes-retired/kubefed | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="kubernetes-retired/kubefed")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem