ctl-architecture

Diagnose Edgion Gateway configuration sync mismatches across center, server, and client cache tiers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Edgion configuration sync issues are hard to diagnose because the same resource can exist in one tier (center, controller server cache, or gateway client cache) but not in another. This Skill helps you pinpoint where the mismatch happens by documenting how edgion-cli targets each tier and routes its API calls.

Core Features & Use Cases

  • Three target modes (center/server/client): Connects to the Controller Admin API or to gateway-side cache endpoints with clear default ports and read/write capability differences.
  • Cache-tier inspection for sync troubleshooting: Compares resource presence and behavior across ConfCenter → ServerCache → ClientCache to locate breakdown stages.
  • Deterministic HTTP client behavior: Uses a structured EdgionClient abstraction (HTTP requests over reqwest) and well-defined API routes per target.
  • Operational commands support: Guides use of get/apply/delete/reload plus non-targeted certificate generation for conf_sync mTLS.
  • Structured output options: Produces table/json/yaml/wide outputs so you can diff results across tiers.

Quick Start

Run the skill by executing edgion-cli get httproute my-route -n default -o yaml first in center mode, then in server mode, then in client mode to see exactly where the sync diverges.

Frequently Asked Questions about ctl-architecture

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

FAQPage Schema
How do I troubleshoot Edgion Gateway configuration sync mismatches across cache tiers?▼

Troubleshoot Edgion configuration sync mismatches by retrieving the same HTTPRoute resource from center, server cache, and client cache tiers using edgion-cli to pinpoint exactly where the sync diverges.

What is the best way to debug gRPC sync versus processing stages for HTTPRoute resources?▼

Debug gRPC sync versus processing stages by running edgion-cli in center, server, and client target modes to compare resource presence and behavior across the ConfCenter, ServerCache, and ClientCache tiers.

How do I validate CRUD effects on Edgion cache propagation using edgion-cli?▼

Validate CRUD effects on cache propagation by executing edgion-cli get, apply, delete, and reload commands against different target modes to observe how resource changes propagate from the center to the client cache.

Does the Edgion configuration sync workflow support structured output for tier-to-tier comparison?▼

Yes, Edgion configuration sync troubleshooting supports structured outputs including table, json, yaml, and wide formats, allowing you to easily diff resource results across cache tiers.

Can I generate mTLS certificates for conf_sync without targeting a specific cache tier?▼

Yes, you can generate certificates for conf_sync mTLS using non-targeted certificate generation commands within edgion-cli, independent of the center, server, or client target selection modes.

Why does my HTTPRoute resource exist in the center tier but fail to sync to the gateway client cache?▼

An HTTPRoute resource may exist in the center tier but fail to sync to the client cache due to breakdowns in the ConfCenter to ServerCache to ClientCache propagation chain, which requires tier-to-tier comparison to locate.