Halaman ini diterjemahkan oleh mesin. Baca versi asli dalam bahasa Inggris.

Recipe

envoy-ai-gateway-operator

Installs the Envoy AI Gateway control plane through the project's own Helm chart, referenced as an artifact in a container registry at the release the controller image comes from. The chart's render carries the controller Deployment and its arguments, the Service Envoy Gateway, the cluster's API server and a metrics scraper reach it on, its service account, the cluster role and binding granting what the project's chart grants, a cluster role letting Envoy Gateway read inference pools, and the mutating webhook configuration that adds the AI external processor to each Envoy Gateway data-plane pod. That Service's /metrics address on 8080 is provides.metrics_endpoint. Beside the chart it emits the six AI Gateway custom-resource definitions, carried beside this Recipe exactly as the project's definitions chart publishes them at the same release. The webhook's serving certificate comes from cert-manager by default: the chart's Certificate and self-signed Issuer are rendered, so cert-manager must already run in the cluster. With infra.webhook_tls_secret set it is the certificate in the Secret that key names, which the operator creates beforehand: no Certificate or Issuer is rendered, cert-manager is not needed, and the Secret the chart would otherwise generate is left out. Every namespaced resource lands in the namespace the Release declares for the component, or in `default` where none is declared; the controller expects the Envoy Gateway it extends in `envoy-gateway-system`, the chart's own default. The controller's MCP session-encryption seed is read when it starts from the Secret infra.mcp_session_seed_secret names, and is otherwise the chart's published default.

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:66aef5d000b46c703897c9fdc5789011aec9e610744d62da8e1396ac3f541594
Dipublikasikan
2026-11-10T10:23:23Z
Identitas penandatangan
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Tanda tangan

  • Resmiapplication/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:75c102a3032306ddcd5f737a837f6d626829f61157adcb1cb3404e6e9453807b

Referensi pada versi ini

oci://hub.aggrega.ai/recipe/helm/envoy-ai-gateway-operator:1.0.0
Target
—
Mengimplementasikan
core/gateway/envoy-ai-gateway-operator:1.0.0

Menyediakan

Templat pointer deterministik yang dihubungkan resep ini untuk konsumen.

NamaTemplat
host{{ .context.rendered_name }}
port1063
metrics_endpointhttp://{{ .context.rendered_name }}:8080/metrics

Workload

Tidak ada templat beban kerja yang dideklarasikan.

Nilai lokal

Tidak ada nilai lokal yang dideklarasikan.

Pemetaan values

Tidak ada pemetaan values yang dideklarasikan.

Relasi

Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.

Menggunakan

Digunakan oleh

Tidak ada apa pun di katalog yang bergantung pada entitas ini.

Referensi konsep Recipe →

Katalog Aggrega — indeks terbuka berisi komponen, fitur, resep, dan plugin yang merendernya.

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi