Esta página foi traduzida automaticamente. Leia o original em inglês.

Recipe

envoy-gateway

An Envoy Gateway ingress gateway via the project's own Helm chart, from a container registry: the controller and its access control, the certificate-generation job and — unless infra.install_crds is false, when infra.control_plane_present must be true or the build halts — the routing API's experimental-channel definitions. Beside the chart this Recipe emits the gateway class, claimed under the controller name the control plane answers for, and the gateway with one HTTP listener. Where infra.tls_secret names a certificate Secret, the gateway gains an `https` listener on port 443 terminating TLS with it; the Secret is referenced and never emitted. It emits neither the data plane, which the control plane creates, nor a namespace. Wired to the AI gateway controller on the extension socket, the control plane names it as its extension server, and the gateway must sit in envoy-gateway-system. Each model on the models socket gets a rule of one AI route and the resources reaching its published endpoint, its credential named only by its Secret; the project's client traffic policy raises the gateway's buffer to 50Mi. With a model wired, provides.host is the data-plane Service Envoy Gateway creates and provides.endpoint its /v1 base URL, qualified with envoy-gateway-system. The route's one traffic policy holds core/period-budget as a rate limit on the route's token cost, counted in the cache socket's store, over TLS to one publishing valkey-tls or redis-tls, core/retry-policy as a retry count, and core/concurrency-limit as a per-model cap on requests in flight. core/audit-logging is the gateway's access log, adding the model and token counts.

Procedência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como publicador oficial.
Digest do conteúdo
sha256:b79a11107ac2a31444f9f5a1977128382a1d2620c5aefef47f1329ba34c98ad1
Publicado
2026-11-10T10:23:25Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:afea069df74369b6107a7d0cc2daf52d7f2e5bf7d7a4bd1a116bd48e4d7434c6

Referência nesta versão

oci://hub.aggrega.ai/recipe/helm/envoy-gateway:1.0.0
Destino
—
Implementa
core/gateway/envoy-gateway:1.0.0

Fornece

Modelos de ponteiros determinísticos que esta receita liga para os consumidores.

NomeModelo
host{{- with optional .values "model" "" }}{{- $key := printf "%s/%s" $.locals.controller_gateway_namespace $.context.rendered_name }}{{- $base := replace "/" "-" $key }}{{- if gt (len $base) 48 }}{{- $base = trimSuffix "-" (trunc 48 $base) }}{{- end }}envoy-{{ $base }}-{{ trunc 8 (sha256sum $key) }}{{ end }}
port{{ .infra.port }}
protocolhttp
endpoint{{- with optional .values "model" "" }}{{- $key := printf "%s/%s" $.locals.controller_gateway_namespace $.context.rendered_name }}{{- $base := replace "/" "-" $key }}{{- if gt (len $base) 48 }}{{- $base = trimSuffix "-" (trunc 48 $base) }}{{- end }}http://envoy-{{ $base }}-{{ trunc 8 (sha256sum $key) }}.{{ $.locals.controller_gateway_namespace }}.svc.cluster.local:{{ $.infra.port }}/v1{{ end }}
model{{ optional .values "model" "" }}
metrics_pod_selectorapp.kubernetes.io/name=envoy,app.kubernetes.io/component=proxy,gateway.envoyproxy.io/owning-gateway-name={{ .context.rendered_name }}
metrics_pod_portmetrics
metrics_path/stats/prometheus

Workload

Nenhum modelo de carga de trabalho declarado.

Variáveis locais

NomeModelo
controller_gateway_namespaceenvoy-gateway-system
model_headerx-ai-eg-model
token_cost_namespaceio.envoy.ai_gateway

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.

Usa

  • implementaimplementacontrato compatível

    core/gateway/envoy-gateway:1.0.0

    Todas as saídas obrigatórias são atendidas e cada saída fornecida é nomeada no contrato.

Usado por

Nada no catálogo depende desta entidade.

Referência do conceito Recipe →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design compartilhado do Aggrega.

Privacidade