Lattice Hub Docs
What is Lattice Hub?

Integration options

Choose Console, SDK, Kubernetes Controller, Pole Sidecar, or protocol adapters for Lattice Hub.

Integration paths follow where the workload runs. Platform teams usually deploy the Control Plane and Console first, then choose SDK, Kubernetes Controller, or Pole Sidecar.

See Concepts and terminology for vocabulary boundaries.

Paths

ScenarioStart hereNotes
Platform managementUsing the ConsoleServices, config, governance, users, and policies.
Control-plane deployServer installationControl Plane, MySQL, and bootstrap config.
Proxyless clientsRust SDKDirect discovery/config/governance consumption.
Thin SDK + SidecarThin SDKMulti-language contract cores (Go / Java / Python / Node.js / C++ / C#) via Sidecar Session and TargetService for local Pole Sidecar.
Kubernetes clustersKubernetes ControllerService sync, annotations, injection.
Local data planePole SidecarHTTP/gRPC forwarding beside the app.
Protocol / gatewaySpecificationShared contracts and multi-protocol adapters.
API integrationAPI and protocolsPort matrix, HTTP OpenAPI, gRPC, xDS, and compatibility entries.

Port cheat sheet

Authoritative detail: Protocol ports. Common defaults:

PurposeDefault port
Console8080
HTTP API8090
Discovery gRPC8091
Config gRPC8093
xDS v315010
Eureka8761
Nacos8848
Apollo8890

Compatible protocol ports follow deploy/conf/pole-apiserver.yaml; they listen only when the matching entry is enabled.

  1. Read the product overview and features.
  2. Deploy the control plane and verify Console plus cache refresh.
  3. Pick one runtime path: SDK, Controller, or Sidecar.
  4. Put configuration and governance behind progressive delivery and rollback.

On this page