Compatibility
Compatibility protocols
Eureka, Nacos, and Apollo compatibility ports, boundaries, and per-protocol API indexes.
The control plane exposes compatibility entry points for Eureka, Nacos, and Apollo so legacy clients can migrate onto a unified control plane. Traffic lands in the same service / config / auth model—not a full third-party server reimplementation.
Prefer gRPC or HTTP OpenAPI for new work. This section lists adapted APIs and how to call them.
Ports and plugins
| Plugin | Default port | Surface | Docs |
|---|---|---|---|
service-eureka | 8761 | Discovery (HTTP) | Eureka |
service-nacos | 8848 (HTTP); gRPC defaults to 9848 | Discovery + config (HTTP v1 subset; 2.x clients often use gRPC) | Nacos |
service-apollo | 8890 | Config pull / notifications (read-only) | Apollo |
Authoritative config: deploy/conf/pole-apiserver.yaml. Keep the matching - name: service-* block to listen.
Product boundaries
- Unified control plane, not a parallel store.
- Common client paths only—do not assume every admin/console API exists.
- Coexist with native entries for migration windows; switch to native protocols when you can change clients.
- Authorization: adapters extract identity, then share the auth chain. See Authorization and resources.