eg-contrib-architecture

Explain Envoy Gateway codebase architecture, translation pipeline, and runner pattern.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a comprehensive map of the Envoy Gateway codebase architecture, detailing the translation pipeline, directory layout, and runner pattern to help contributors navigate the repository.

Core Features & Use Cases

  • Architectural overview of the translation pipeline, resource flow, and data structures (CRDs, IRs, and xDS components).
  • Directory layout and runner pattern documentation, including the interaction between providers, translators, and infra managers.
  • Use case guidance for contributors and maintainers to understand end-to-end workflows and extension points.

Quick Start

Explain the repository's architecture and summarize the core components of the Envoy Gateway project.

Frequently Asked Questions about eg-contrib-architecture

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

FAQPage Schema
How does the Envoy Gateway translation pipeline work?

The Envoy Gateway translation pipeline processes CRDs through providers, translates them into XdsIR and InfraIR resources, and generates xDS components to configure the gateway runtime.

What is the runner pattern in Envoy Gateway architecture?

The runner pattern in Envoy Gateway organizes runtime components so providers, translators, and infra managers interact sequentially to process ProviderResources and deploy gateway infrastructure.

How do I navigate the Envoy Gateway codebase directory layout?

The Envoy Gateway codebase directory layout maps providers, translators, and infra managers into structured layers, separating CRD definitions, IR data types, and xDS component generation.

How do ProviderResources, XdsIR, and InfraIR interact in Envoy Gateway?

ProviderResources feed into the translation pipeline where they are concurrently converted into XdsIR for xDS configuration and InfraIR for infrastructure management, enabling end-to-end gateway deployment.

Can I use this to understand extension points for Envoy Gateway contributors?

Yes, it maps end-to-end workflows and extension points across the translation pipeline, detailing how contributors can extend CRDs, IRs, and runners within the Envoy Gateway architecture.

When do I need to understand xDS components in Envoy Gateway?

Understanding xDS components is necessary when extending or deploying Envoy Gateway, as they represent the final output of the translation pipeline that configures the downstream Envoy proxies.