eg-fundamentals

Clarify Envoy Gateway resource hierarchies and CRD relationships for Kubernetes traffic routing.

3|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/missBerg/envoy-skills --skill eg-fundamentals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eg-fundamentals
Source: https://github.com/missBerg/envoy-skills/tree/main/gateway/adopters/skills/eg-fundamentals
Command: npx skills add https://github.com/missBerg/envoy-skills --skill eg-fundamentals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, practical guide to understanding Envoy Gateway resource hierarchies, CRD relationships, naming conventions, and resource organization, helping teams design correct, scalable traffic routing configurations in Kubernetes.

Core Features & Use Cases

  • Clarifies the Resource Hierarchy: GatewayClass -> Gateway -> Routes -> BackendRefs and how they bind to controllers and services.
  • Documents Envoy Gateway Extension CRDs: EnvoyProxy, ClientTrafficPolicy, BackendTrafficPolicy, SecurityPolicy, EnvoyExtensionPolicy, EnvoyPatchPolicy, Backend, HTTPRouteFilter and their target resources.
  • Summarizes Naming & Structural Conventions: kebab-case naming, namespace scoping, unique listener combinations, and consistent labeling practices.
  • Describes Policy Attachment Model: how policies target Gateways or Routes with most-specific wins.
  • Use Cases: guiding adoption, architecture planning, and end-to-end configuration of Gateway-based traffic routing.

Quick Start

Review the Gateway API hierarchy and implement a minimal GatewayClass, Gateway, and Routes setup following the examples.

Frequently Asked Questions about eg-fundamentals

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

FAQPage Schema
How do Envoy Gateway CRDs relate to each other for traffic routing?

Envoy Gateway CRDs follow a hierarchy where GatewayClass binds to a controller, Gateway defines listeners, and Routes attach to Gateways to reference Backend services. This structured relationship ensures correct traffic routing configuration.

What is the correct way to configure Envoy Gateway policies in Kubernetes?

Envoy Gateway uses a policy attachment model where policies like ClientTrafficPolicy and SecurityPolicy target Gateways or Routes. The most-specific policy wins, allowing granular traffic control and consistent resource design across your deployment.

How do I set up a minimal Gateway API configuration for Envoy Gateway?

To set up Envoy Gateway, implement a minimal configuration starting with a GatewayClass, then define a Gateway with listeners, and finally create HTTPRoute resources. Follow kebab-case naming and namespace scoping conventions for consistent resource design.

Which Envoy Gateway extension CRDs target Gateway and Route resources?

Envoy Gateway extension CRDs include ClientTrafficPolicy, BackendTrafficPolicy, SecurityPolicy, EnvoyExtensionPolicy, and EnvoyPatchPolicy. These extensions target Gateway or Route resources to apply specific traffic, security, and proxy customization rules.

What naming conventions should I follow for Envoy Gateway resources?

Envoy Gateway resources should use kebab-case naming, namespace scoping, unique listener combinations, and consistent labeling practices. Adhering to these structural conventions ensures scalable and organized traffic routing configurations.

Can I use Envoy Gateway for architecture planning and traffic routing adoption?

Yes, Envoy Gateway is suited for guiding adoption and architecture planning. It clarifies resource hierarchies and CRD relationships, helping adopter engineers design and validate end-to-end Gateway-based traffic routing configurations.