Implementing Translation for a New Feature

Prerequisites

• The API types already exist (see eg-contrib-add-api) — API changes must be in a separate PR
• Read eg-contrib-architecture — understand the pipeline: CRD → IR → xDS
• Read eg-contrib-envoy-internals — understand how Envoy uses the xDS config you generate

Phase 1: Add IR Types

File: internal/ir/xds.go

1.1 Define the IR struct

The IR should represent the intent of the feature, not the Envoy xDS structure. It is Envoy-agnostic.