k8gb-io/k8gb

A cloud native Kubernetes Global Balancer observed · 2026-08-28

github.com/k8gb-io/k8gb · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

92/100

Activity 99
Release rhythm 79
Longevity 100

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: 65
age_days: 2471
days_rel: 61
days_push: 7
n_releases_24m: 8

Full methodology

Adoption not part of the score

1302 stars · 162 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

K8GB (Kubernetes Global Balancer) is a CNCF Incubating, open-source global server load balancing (GSLB) solution for Kubernetes, implemented as a Kubernetes operator in Go. It load-balances traffic across geographically dispersed Kubernetes clusters using DNS-based strategies (failover, round-robin, weighted) configured via a single Gslb CRD, with integrations for Route53, Infoblox, Cloudflare, NS1, Azure DNS, and RFC2136-compatible DNS servers.

Use cases

load balance traffic across multiple Kubernetes clusters in different regions
configure DNS failover between primary and secondary Kubernetes clusters for high availability
replace proprietary hardware GSLB appliances with a cloud native solution
enable global load balancing for a Kubernetes Ingress using a single CRD
use Kubernetes liveness and readiness probes to drive global traffic routing decisions
set up multi-cluster DNS-based load balancing with Route53 or Cloudflare
avoid a single point of failure in global load balancing without a dedicated management cluster

When to choose

you run Kubernetes workloads across multiple geographic regions or clusters and need DNS-based global load balancing
you want a Kubernetes-native GSLB managed via CRDs and Helm instead of proprietary network vendor appliances
you need region failover, round-robin, or weighted round-robin strategies driven by Kubernetes health probes
you use Route53, Infoblox, Cloudflare, NS1, Azure DNS, or RFC2136-compatible DNS providers
you want an open-source, CNCF-governed solution with no single point of failure

When to avoid

you only need load balancing within a single Kubernetes cluster (a standard Service or Ingress controller suffices)
you need layer-4/layer-7 proxying or traffic splitting at the request level rather than DNS-level routing
your environment cannot use or expose DNS as the traffic steering mechanism
you require latency-based routing with sub-second failover, since DNS TTLs introduce propagation delays
you are not running Kubernetes, as k8gb is tightly coupled to the Kubernetes ecosystem

Facets

service · maturity active

networking service-discovery routing cloud-computing networking infrastructure-as-code microservices cloud self-hosted go gslb global-load-balancing dns-based-load-balancing cncf-incubating multi-cluster kubernetes-operator failover route53 infoblox cloudflare helm-chart cross-region load-balancing kubernetes devops high-availability docker

3 sources

readme: https://github.com/k8gb-io/k8gb · fetched 2026-08-28 · c9ee6e299a2d
homepage: https://www.k8gb.io/latest/ · fetched 2026-08-29 · 905cca3fe5f2
site_page: https://www.k8gb.io/latest/tutorials · fetched 2026-08-29 · 7b3419ee6204

Member repositories

Repository	Role	Health v2
k8gb-io/k8gb	main	92

For agents

markdown · JSON · MCP: product_card(name="k8gb-io/k8gb")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem