eg-route

Generate HTTP, gRPC, TCP, UDP, and TLS routing manifests for Envoy Gateway.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route management for Envoy Gateway to direct multi-protocol traffic across HTTP, gRPC, TCP, UDP, and TLS.

Core Features & Use Cases

  • Generates HTTPRoute, GRPCRoute, TCPRoute, UDPRoute, or TLSRoute resources bound to a Gateway.
  • Supports host-based matching, multiple routing rules per route, filters, and cross-namespace references.
  • Use case: route different protocols to distinct backends behind a single Gateway for unified ingress management.

Quick Start

Set the Type and Hostname defaults if missing, then generate and apply the appropriate Route manifest (HTTPRoute, GRPCRoute, TCPRoute, UDPRoute, or TLSRoute) to the Gateway.

Frequently Asked Questions about eg-route

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

FAQPage Schema
How do I configure multi-protocol routing rules for an Envoy Gateway?

You can route multiple protocols through a single Envoy Gateway by creating distinct HTTPRoute, GRPCRoute, TCPRoute, UDPRoute, and TLSRoute manifests. Each manifest binds to the Gateway using parentRefs and directs traffic to distinct backends.

Can I route gRPC and TCP traffic to distinct backends behind a single Gateway?

Yes, you can route gRPC and TCP traffic to distinct backends behind a single Gateway. By generating GRPCRoute and TCPRoute manifests with specific backendRefs, you direct each protocol to its appropriate destination independently.

Does Envoy Gateway support cross-namespace backend references in Route manifests?

Yes, Envoy Gateway supports cross-namespace backend references in Route manifests. You can configure backendRefs to point to services in different namespaces, enabling multi-protocol traffic direction across namespace boundaries within your cluster.

What is the best way to set up host-based matching for TLS routes?

The best way to set up host-based matching for TLS routes is by generating a TLSRoute manifest. This resource configures hostnames and parentRefs to securely direct encrypted traffic to the correct backend services.

How do I apply multiple routing rules and filters to a single HTTPRoute?

To apply multiple routing rules and filters, generate an HTTPRoute manifest with multiple rule definitions. Each rule can specify host-based matches and filters, allowing granular control over HTTP traffic directed to your backendRefs.