architecture

Explain Edgion's Controller–Gateway–Center architecture and its runtime sync flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the time it takes to understand Edgion’s Controller–Gateway–Center architecture by giving you a structured, cross-component mental model of how configuration is processed, synced, and applied at runtime.

Core Features & Use Cases

  • Understand the end-to-end control/data flow: track how resources move from event sources through the Controller pipeline into Gateway runtime stores via gRPC.
  • Learn the synchronization contract: map ConfigSync RPC methods, versioning, watch/list behavior, and reconnection/relink semantics.
  • Find extension and troubleshooting entry points: identify where to add a new plugin/resource/connector and where to debug route/TLS/plugin execution issues.
  • Use real design constraints: understand preparse/runtime separation, cache tiers, ArcSwap hot updates, and plugin execution phase rules (including body-phase logging constraints).

Quick Start

Use the architecture skill to explain how a change in an HTTPRoute becomes an updated Gateway route table and which components you should inspect if the Gateway does not reflect the change.

Frequently Asked Questions about architecture

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

FAQPage Schema
How does the Edgion Controller process HTTPRoute changes into Gateway runtime behavior?

The Edgion Controller pipeline processes HTTPRoute changes by moving resources through cache tiers and hot-syncing them into Gateway runtime stores via gRPC. This applies updated proxy routing behavior dynamically using lock-free ArcSwap reads.

How do I debug TLS routing or plugin execution issues in a Kubernetes Gateway setup?

Debug TLS routing and plugin execution issues by inspecting the Controller-to-Gateway gRPC sync contract and runtime proxy stores. The architecture maps plugin execution phase rules and version tracking to pinpoint sync failures.

What is the gRPC synchronization contract for the Edgion Controller and Gateway?

The gRPC synchronization contract defines ConfigSync RPC methods, versioning, and watch/list behavior to sync resources. It establishes reconnection and relink semantics to maintain consistent runtime proxy behavior across distributed components.

Where do I add a new plugin or connector in the Edgion Controller-Gateway-Center architecture?

Add new plugins or connectors at specific extension points within the Controller pipeline before preparse and runtime separation. The architecture blueprint identifies these entry points to ensure proper resource processing and hot reload integration.

Why are my Gateway route table updates not reflecting after a configuration sync?

Gateway route table updates may fail due to readiness gates blocking application or broken gRPC sync relinks. Check version tracking and lock-free ArcSwap read operations to verify if the runtime proxy store received the hot update.