← Back to Kube-Zen

Network-Level Single-Active Routing for Kubernetes

Zero code changes required - Annotate a Service and zen-lead creates leader Service + EndpointSlice

Coming SoonOpen Source

What is zen-lead?

zen-lead is a non-invasive leader election controller for Kubernetes that provides network-level single-active routing without requiring application code changes or mutating workload pods.

Key Differentiation: Unlike client-go leader election libraries (which require application code changes), zen-lead provides a network contract that works for any client, any language, without code changes. Simply annotate a Service and connect to the leader Service endpoint.

Key Features

✨

Zero Code Changes

Applications don't need to know about leader election - just connect to the leader Service

πŸ”§

Non-Invasive

No pod mutation, no changes to user resources - only creates leader Service and EndpointSlice

⚑

Automatic Failover

Controller-driven leader selection based on pod readiness with fast failover (1.0-1.3s average)

πŸ”’

Production-Ready

Secure defaults, namespace-scoped, event-driven reconciliation, HA controller with leader election

πŸ“Š

Observable

Prometheus metrics, Grafana dashboards, and alert rules for full visibility

☸️

Kubernetes-Native

Uses standard Kubernetes primitives - no CRDs, no webhooks, no pod mutation

How It Works

1

Annotate Your Service

kubectl annotate service my-app zen-lead.io/enabled=true
2

zen-lead Creates Leader Service

Automatically creates my-app-leader Service (selector-less) and EndpointSlice pointing to leader pod

3

Connect to Leader Service

# Update your application config
env:
- name: SERVICE_NAME
  value: my-app-leader  # Points only to current leader

Get Started

zen-lead is coming soon! Check out the repository and feel free to contribute.