03-resources

Consolidate Edgion Kubernetes Gateway API resource schemas into a numbering-aligned YAML reference.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of finding authoritative, field-level Kubernetes and Edgion CRD schemas quickly, so you can author correct Gateway API and Edgion resource manifests without guessing defaults or formats.

Core Features & Use Cases

  • Provides a unified feature reference for Edgion’s Gateway API standard resources and Edgion extension resources, aligned with the repository’s architecture numbering.
  • Documents full schemas and key fields (including parentRef/backendRef concepts, route matching, TLS/mTLS settings, plugin configurations, health checks, and connector configuration).
  • Supports implementation-to-document mapping so readers can cross-reference what the controller expects versus what manifests specify.

Quick Start

Ask for the complete YAML schema and field meanings for the Gateway resource, including listener TLS options and AllowedRoutes configuration.

Frequently Asked Questions about 03-resources

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

FAQPage Schema
How do I configure TLS routing and listener options for Kubernetes Gateway API resources?

Gateway API TLS routing is configured by referencing field-level YAML schemas for listener TLS options and AllowedRoutes, ensuring manifests match the controller's expected architecture numbering for correct traffic routing.

What is the correct CRD schema for Edgion extension resources and plugin configuration?

The Edgion extension resource CRD schema defines plugin configurations and external connectors, consolidating field-level YAML guidance and frontmatter descriptions to support manifest authoring and troubleshooting.

How do I write manifests for Edgion backends and route matching across Kubernetes modes?

Authoring Edgion backend and route matching manifests requires extracting backendRef and parentRef concepts from the unified feature reference, applying field-level YAML formats that align with the repository's architecture numbering across Kubernetes modes.

Does the Edgion resource reference support mTLS settings and ACME configurations?

Yes, the Edgion resource reference documents full schemas for mTLS settings and ACME configurations, providing field-level YAML guidance to map implementation expectations directly to manifest specifications.

Why does my Edgion Gateway manifest fail validation against the controller's expected CRD schema?

Manifest validation often fails when YAML fields do not match the authoritative Edgion CRD schema; cross-referencing the implementation-to-document mapping ensures your route matching, TLS, and plugin fields align with the correct architecture numbering.

Can I use this reference to troubleshoot external connector configurations in Edgion?

Yes, you can troubleshoot external connector configurations by extracting the frontmatter name and description for resource discovery, then applying the field-level YAML guidance specific to Edgion's extension resources.