05-resources

What problem does it solve?

It turns a complex, multi-stage resource synchronization pipeline into an understandable, repeatable architecture for Edgion’s Controller-to-Gateway processing, including how validation, parsing, status, and requeue cascades interact across resource types.

Core Features & Use Cases

• Common processing flow: explains the shared end-to-end chain from resource change events (Kubernetes watch / filesystem watch) through Controller ResourceProcessor stages into Gateway runtime activation.
• Per-resource behavioral breakdown: documents the concrete logic for each resource’s handler stages (filter, validate, preparse/parse, on_change/on_delete, update_status) and key special handling (e.g., Secrets not synced, plugin metadata resolution, TCP/UDP/HTTP routing differences).
• Cross-resource dependency mapping: summarizes how resources depend on each other via stores and managers (SecretRefManager, ServiceRefManager, CrossNsRefManager, GatewayRouteIndex, PluginMetaData refs) and how changes cascade through requeues.

Quick Start

Use the 05-resources skill to explain how a specific resource (for example, HTTPRoute) moves through Controller parsing and becomes active routing configuration in the Gateway, including what requeues are triggered when referenced Secrets or Gateways change.