Component ecosystem

From control plane to runtime, components collaborate on one resource model.

Control Plane (embedded Console; Limiter as an optional in-repo process) defines the governance model and multi-protocol entry; Rust SDK, Thin SDK, Controller, Pole Sidecar, and Specification cover Proxyless / Sidecar access, cluster sync, local data plane, and open contracts.

Read component docs View GitHub organization

COMPONENTRESPONSIBILITYIMPLEMENTATION NOTES

Control Plane

Unified discovery, configuration, governance, identity, Registry, and multi-protocol access; embedded Console; Limiter ships in the same artifact as an optional process mode.

Management API, multi-protocol entry, and embedded ConsoleLimiter: limiter-server / full modes

Rust SDK

Lightweight Proxyless Service Governance access for Rust applications.

crate: pole_rust = "0.2.0"Rust >= 1.63.0

Thin SDK

Framework-independent Thin SDK cores for Go, Java, Python, Node.js, C++, and C# that join the local Pole Sidecar via Sidecar Session and TargetService v1.

Go / Java / Python / Node.js / C++ / C#Node.js 0.2.1 · C# 0.1.0-ALPHA.46 · Java 0.1.0-SNAPSHOT

Kubernetes Controller

Connects Kubernetes to the control plane; syncs Service, Endpoints, Namespace, and ConfigMap.

Full / on-demand and bidirectional configuration syncPole Sidecar, Java Agent, and Envoy injection

Pole Sidecar

Pingora-based lightweight data-plane skeleton supporting HTTP, HTTP/2, and gRPC-h2c forwarding.

Prefix routing and round-robin load balancingDynamic governance access still evolving on the roadmap

Specification

Open service governance and protobuf protocol definitions covering governance, security, and MCP.

Java / Go / Rust generation entry pointsShared protocol contracts across components