annotations-features

Document Edgion `edgion.io/*` annotation keys and option scopes for Gateway API resources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Edgion configuration often relies on many edgion.io/* annotations and related option keys, and it can be hard to know which key applies to which resource and how it behaves.

Core Features & Use Cases

  • One-stop annotation reference: Quickly locate keys by topic, including Gateway, HTTPRoute/GRPCRoute, TCPRoute/TLSRoute, and EdgionTls.
  • Options and label clarity: Distinguish between metadata.annotations, tls.options, spec.options, and related labels so you set the value in the correct place.
  • Developer checklist for extensions: Use the add-new-annotation checklist to ensure new keys are classified, parsed, documented, and tested consistently.
  • System/test key awareness: Identify system-managed and test-only keys to avoid accidental misconfiguration.

Quick Start

Use the annotations overview to look up an annotation key like edgion.io/forward-raw-path, then open the detailed metadata or options reference to apply it to the correct Gateway API resource field safely.

Frequently Asked Questions about annotations-features

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

FAQPage Schema
Where do I set Edgion annotations on Kubernetes Gateway API resources?

Edgion annotations are placed in metadata.annotations, tls.options, or spec.options depending on the key. Use the reference to distinguish placement rules for Gateway, HTTPRoute, GRPCRoute, TCPRoute, TLSRoute, and EdgionTls resources to apply values correctly.

How do I find the correct value format and defaults for edgion.io annotations?

Search the structured reference by topic or key name to find value formats and defaults for edgion.io annotations. It documents per-key defaults, value formats, and scope to ensure reliable discovery for day-to-day configuration.

What is the difference between tls.options and spec.options in Edgion configuration?

The difference between tls.options and spec.options is their placement scope on Gateway API resources. The reference clarifies these option keys alongside metadata.annotations and related labels so you set values in the correct place.

Are there reserved Edgion annotations for system or test configurations?

Yes, there are system-managed and test-only Edgion annotations. The reference identifies these reserved keys to help you avoid accidental misconfiguration and distinguish them from user-configurable option keys.

How do I add and classify a new edgion.io annotation key for controller runtime?

Use the developer checklist to add a new edgion.io annotation key, ensuring it is classified, parsed, documented, and tested consistently. This maintains reliable discovery and implementation workflows for controller runtime extensions.