aigw-backend

Automates pairing Envoy Gateway Backend with AIServiceBackend via backendRef for AI provider routing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the pairing of an Envoy Gateway Backend with an AIServiceBackend to route AI provider requests through a Kubernetes-backed API gateway.

Core Features & Use Cases

  • Create the Backend with a fully qualified domain name (fqdn) and port for HTTPS endpoints to represent the external AI provider.
  • Create the AIServiceBackend using a defined schema (OpenAI, Anthropic, AWS Bedrock, Azure OpenAI, Vertex AI, Cohere, etc.) and reference the Backend via backendRef.
  • Optionally attach a BackendTLSPolicy for secure TLS termination and enable in-cluster or cloud-hosted backends as needed.
  • Use cases include connecting providers like OpenAI or Vertex AI to Envoy Gateway for managed routing, schema validation, and secure traffic.

Quick Start

Define the Backend with the external hostname and port, then create an AIServiceBackend that references that Backend.

Frequently Asked Questions about aigw-backend

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

FAQPage Schema
How do I route OpenAI or Anthropic requests through an Envoy Gateway in Kubernetes?

You can route AI provider requests by creating an Envoy Gateway Backend with an FQDN and port, then pairing it with an AIServiceBackend using a backendRef to connect providers like OpenAI or Anthropic.

How do I configure an AIServiceBackend for cloud-hosted providers like Vertex AI or AWS Bedrock?

Configuring an AIServiceBackend for providers like Vertex AI or AWS Bedrock requires defining the provider schema and linking it to a Backend via a backendRef, enabling managed routing through your Kubernetes API gateway.

Does Envoy Gateway require a BackendTLSPolicy for HTTPS AI provider endpoints?

Yes, attaching a BackendTLSPolicy is required for secure TLS termination when routing traffic to HTTPS backends representing external AI providers in your Kubernetes cluster.

Can I use Envoy Gateway to manage both in-cluster and external cloud-hosted AI backends?

Yes, Envoy Gateway supports managing both in-cluster and external cloud-hosted AI backends by applying the correct Backend FQDN, port, and AIServiceBackend backendRef linkage for each provider.

What is the best way to enforce schema validation for AI service traffic in Kubernetes?

The best way to enforce schema validation is to create an AIServiceBackend with a defined provider schema, such as OpenAI or Cohere, and route its traffic through an Envoy Gateway Backend.

Why is my AIServiceBackend not routing traffic to my Kubernetes API gateway backend?

Routing fails if the Backend does not expose a proper FQDN and port, or if the AIServiceBackend lacks the correct backendRef linkage and TLS policy for the HTTPS endpoint.