eg-gateway

Generate Kubernetes GatewayClass and Gateway YAML manifests for Envoy Gateway.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring Envoy Gateway in Kubernetes requires creating GatewayClass and Gateway resources with per-listener settings. This skill automates the generation of these manifests to simplify ingress setup for Envoy Gateway.

Core Features & Use Cases

  • Generates a GatewayClass and Gateway resources with HTTP, HTTPS, TLS passthrough, TCP, and UDP listeners.
  • Supports per-listener configuration, including hostnames, ports, and protocol-specific TLS options.
  • Use cases include exposing multiple protocols on a single Gateway or dedicating separate Gateways for isolation.

Quick Start

Provide the Gateway name and protocols to generate the GatewayClass and Gateway manifests.

Frequently Asked Questions about eg-gateway

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

FAQPage Schema
How do I generate Kubernetes Gateway manifests for Envoy Gateway?

To generate Kubernetes Gateway manifests for Envoy Gateway, you provide the Gateway name and desired protocols. The skill outputs GatewayClass and Gateway YAML resources with per-listener configurations for your cluster.

Can I configure multiple listeners like HTTP and HTTPS on a single Envoy Gateway?

Yes, you can configure multiple listeners like HTTP and HTTPS on a single Envoy Gateway. The skill generates manifests supporting http, https, tls-passthrough, tcp, and udp protocols with individual port and hostname settings.

What do I need to include in a Gateway manifest for TLS passthrough?

To configure TLS passthrough in a Gateway manifest, you need to specify the tls-passthrough protocol for your listener. The skill produces the required YAML structure including protocol-specific TLS options and port definitions.

When should I use separate Gateway resources instead of one Gateway for multiple protocols?

You should use separate Gateway resources instead of one Gateway when you need strict isolation between different protocols. The skill supports both exposing multiple protocols on a single Gateway and dedicating separate Gateways.

Does this approach support both TCP and UDP listeners for Kubernetes ingress?

Yes, this manifest generation approach supports both TCP and UDP listeners for Kubernetes ingress. Alongside http and https, you can specify tcp or udp protocols to expose services through the Envoy Gateway.