config-reference

What problem does it solve?

Edgion operators often need to quickly understand which YAML/TOML fields exist, what they do, what defaults apply, and when each configuration layer takes effect—without digging through source code or scattered docs.

Core Features & Use Cases

• Controller TOML schema reference: Provides the complete field definitions for edgion-controller, including server/admin listen settings, logging, validation toggles, configuration sync sizing, conf_center (filesystem vs Kubernetes), federation client options, and admin authentication bootstrap (OIDC and local auth).
• Gateway TOML schema reference: Documents edgion-gateway configuration fields for controller connectivity, logging, Pingora server behavior, business log outputs, global rate-limit tuning, gRPC mTLS client settings, and access-log sensitive redaction.
• EdgionGatewayConfig CRD schema reference: Explains GatewayClass-scoped dynamic configuration, including timeouts, retries, real IP extraction, security protections, global plugins, CORS preflight behavior, reference-grant validation, and path normalization guarantees.
• Operational decision support: Helps you choose the correct configuration layer first (Controller TOML vs Gateway TOML vs CRD) before looking up specific options.

Quick Start

Use the config-reference skill to look up the exact configuration fields you need for your specific change (Controller startup settings, Gateway logging and rate limiting, or GatewayClass-level CRD policies).