center

Explain how edgion-center aggregates Controller federation data into unified metadata views.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill center
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: center
Source: https://github.com/Pandaala/Edgion/tree/main/skills/01-architecture/06-center
Command: npx skills add https://github.com/Pandaala/Edgion --skill center

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand how edgion-center acts as the federation hub, turning many Controllers’ published data into a consistent operational view and exposing it via an Admin API, while persisting controller registry state.

Core Features & Use Cases

  • Federation hub mental model: Clarifies the reverse-watch flow where Center issues watch requests and Controllers push WatchList/WatchEvent updates back.
  • Operational lifecycle & failure modes: Documents startup sequence, registration acceptance rules, heartbeat/timeout behavior, and how offline vs removed controllers are handled.
  • Production-grade API surface for operators: Summarizes the Admin HTTP endpoints and the gRPC FederationSync stream protocol, including validation caps and error-handling outcomes.
  • State architecture: Explains the division of responsibilities across ResourceAggregator, CenterWatchCache/Registry, CenterMetaDataStore, and the SQLite-based controller registry.

Quick Start

Ask an AI to explain how edgion-center aggregates PluginMetaData from Controllers through its bidirectional gRPC reverse-watch stream and how the Admin API serves the aggregated results.

Frequently Asked Questions about center

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does multi-cluster federation aggregation work with a reverse-watch gRPC stream?

Multi-cluster federation aggregation uses a reverse-watch gRPC stream where the control plane issues watch requests and Controllers push WatchList and WatchEvent updates back to merge PluginMetaData into real-time routes.

How do I debug offline or removed Controllers in a Kubernetes multi-cluster topology?

Debug offline or removed Controllers by checking the federation hub's registration validation, heartbeat timeout behavior, and capacity caps to identify whether the Controller state was persisted in the SQLite registry.

What is the best way to expose aggregated multi-cluster metadata to operators via an API?

The best way to expose aggregated multi-cluster metadata is through an Admin HTTP API that serves the unified view collected from the bidirectional gRPC FederationSync stream protocol.

Does the edgion-center control plane support SQLite for persisting controller registry state?

Yes, the control plane supports SQLite for persisting controller registry state, maintaining the registry across startup lifecycle phases and operational restarts.

What are the limitations of using a bidirectional stream protocol for federation sync?

Limitations of the bidirectional stream protocol include strict registration acceptance rules, validation caps on incoming data, and specific error-handling outcomes when Controllers fail heartbeat checks or disconnect unexpectedly.

When do I need a unified control plane for Kubernetes Gateway API multi-cluster topologies?

You need a unified control plane for Kubernetes Gateway API multi-cluster topologies when you must aggregate Controller data, validate registration capacity, and merge PluginMetaData into a consistent operational view.