gateway-api

Document Gateway API compatibility boundaries and conformance test debugging workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand and safely work within Edgion’s intentional Gateway API compatibility boundaries, especially when running conformance tests or changing Gateway/TLS matching behavior.

Core Features & Use Cases

  • Identify intentional deviations: Know which Gateway API features Edgion does not implement and why, so you can interpret conformance outcomes correctly.
  • Run and debug conformance testing efficiently: Use the documented workflows for running core/extended/split-profile suites, including common timeout and status-condition failure modes.
  • Diagnose batch failures reliably: Collect controller/gateway/test logs, correlate timelines, and narrow down failure modes when tests pass individually but fail together.

Quick Start

Ask the AI to explain which Gateway API features in Edgion are intentionally not implemented and summarize the recommended conformance run commands for HTTP/GRPC versus TLS.

Frequently Asked Questions about gateway-api

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

FAQPage Schema
How do I run Gateway API conformance tests for HTTP and TLS routing?

To run Gateway API conformance tests, use the documented workflows for executing core, extended, and split-profile suites, including specific commands for HTTP/GRPC versus TLS to verify routing behavior and compatibility boundaries.

Why do my Gateway API conformance tests pass individually but fail when batched together?

When Gateway API conformance tests pass individually but fail together, correlate controller, gateway, and test logs to narrow down failure modes, checking for timeline overlaps and status-condition mismatches that cause batch execution timeouts.

What Gateway API features are intentionally not implemented in Edgion?

Edgion intentionally does not implement specific Gateway API features, including certain TLS routing and listener-scoped TLS selection behaviors, with documented architectural limitations around TLS and ports to ensure consistent functional expectations.

How do I diagnose Kubernetes Gateway API status condition mismatches?

Diagnose Kubernetes Gateway API status condition mismatches by collecting controller and gateway data-plane logs, correlating timelines across components, and stepping through concrete diagnosis workflows to identify split-profile constraints and feature deviations.

What are the limitations of using split-profile constraints in Gateway API compatibility?

Split-profile constraints in Gateway API compatibility limit certain feature declarations and test execution strategies, requiring teams to understand architectural limitations around TLS and ports to correctly interpret conformance outcomes and status conditions.