本页面为机器翻译。阅读英文原文。

Component

core/gateway/envoy-gateway

An Envoy Gateway ingress gateway, programmed through the Gateway API. Its control plane watches the cluster's GatewayClass, Gateway and route resources and configures an Envoy data plane, which terminates client HTTP traffic — and HTTPS too, where the Release names a certificate Secret through tls_secret — and load-balances it to the Services those routes name. This Component installs the control plane and claims the gateway class and the gateway itself. An application reaches it by declaring a route naming the gateway as its parent, and the gateway is named after the component the Aggregate declares. Realized on Kubernetes through a Helm Recipe; it has no standalone local-container form, so no Compose Recipe is provided. It publishes the pod label, port name and path a scraper discovers its proxies' metrics by. It also serves models through Envoy AI Gateway. Wired to the AI gateway controller on its extension socket, it calls that controller as its extension server, and the Release must place it in envoy-gateway-system or the build halts. Each model on its models socket is served under /v1 at the gateway's address to a request naming the connection's alias, with that connection's credential. The gateway publishes that address as its endpoint, qualified with envoy-gateway-system so an agent in any namespace reaches it, and values.model as its model. While a model is wired, every route on the gateway takes the 50Mi per-connection request buffer Envoy AI Gateway configures. It realizes core/period-budget in tokens, core/retry-policy, core/concurrency-limit per model, and core/audit-logging with no cost or verified caller.

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:3afd79abd963d7eaaa6fc702d5c2288b28bb3c6485a5a4bbb604d919aa3cfe95
发布时间
2026-11-10T10:11:47Z
签名身份
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

签名

  • 官方application/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:d14ea54a288890aca449abf7e0af2ac73fddc7e25fa4ecbdb660e071f92f71bd

此版本的引用

oci://hub.aggrega.ai/component/core/gateway/envoy-gateway:1.0.0

开发者参数

开发者在 Aggregate 中设置的值。

名称类型默认值必需描述
gateway_class_namestringenvoy-gateway否Name of the gateway class this install claims. The gateway declares this class, and the class is cluster-scoped, so two installs sharing a cluster need two different names.
allowed_route_namespacesstring (Same | All)Same否Which namespaces may attach a route to the gateway's listeners. `Same` accepts routes from the gateway's own namespace only, which is what the routing API assumes when nothing says otherwise; `All` accepts routes from every namespace. Stated explicitly so the narrower of the two is a choice a reader can see rather than a default they meet later.
modelstring—否The alias of a connection on the models socket that this gateway publishes as its model, the model name a component wired to the gateway sends. It must be an alias a models connection carries, and the build halts naming this value otherwise; it is required while the models socket holds a connection, and omitted while it holds none.

运维规格

运维人员按环境调整的基础设施规格。

名称类型默认值必需描述
imagestringdocker.io/envoyproxy/gateway:v1.9.1否Control-plane container image the gateway's controller runs. Set this to pull the same release from a mirror or a private registry.
controller_namestringgateway.envoyproxy.io/gatewayclass-controller否Controller name the gateway class is claimed under. The control plane is configured to answer for this same name, so the two halves cannot disagree; change it only where a second control plane in the cluster already answers for the default.
portinteger (min 1, max 65535)80否HTTP port the gateway's plain HTTP listener accepts client traffic on. Most operators should omit this and let the Recipe assign the default (80).
tls_secretstring—否Name of an existing Secret of type kubernetes.io/tls, in the gateway's own namespace, holding the certificate and private key the gateway presents to clients. Set, the gateway gains a second listener named `https`, on port 443 with protocol HTTPS, which terminates TLS with that certificate beside the plain HTTP listener; a route attaches to it alone by naming that listener, and to both by naming none. Left unset, the gateway carries its plain HTTP listener alone. The Secret is referenced and never created here; it is the operator's, or a certificate controller's, to provide.
install_crdsbooleantrue否Whether this Release installs the custom-resource definitions the gateway and its routes are written against, together with the upgrade-safety policy that guards them. Set false where the cluster manages those definitions separately, and affirm control_plane_present when you do.
control_plane_presentbooleanfalse否Affirms that the custom-resource definitions this Release does not install are already present in the target cluster. The compiler runs ahead of time and cannot inspect a cluster, so it asks rather than checks. With install_crds set false and this left unaffirmed, the build halts rather than emitting a gateway class and a gateway that nothing would reconcile.
source_versionstring—否Source artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility.
computeobject—否—
overridesobject (open)—否Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

输出契约

此组件通过 uses 拓扑向使用方发布的值。

名称类型默认值必需描述
hoststring—否In-cluster DNS name of the Service Envoy Gateway creates for this gateway's data plane, in the gateway's own namespace, the name alone without a namespace; a consumer in another namespace qualifies it with envoy-gateway-system, where the gateway sits while a model is wired, as endpoint already does. A consumer sends its client traffic here rather than to the service behind the gateway. Empty while nothing is wired to the models socket.
portinteger—是TCP port that Service accepts the gateway's plain HTTP listener on, infra.port.
protocolstring—否How the published address is spoken to — `http`, so a consumer composes an address on that scheme.
endpointstring—否Full base URL of the OpenAI-compatible API the gateway serves for the models wired to its models socket, with the host, the port and the /v1 path already composed. The host is qualified with envoy-gateway-system, the namespace the build requires the gateway to sit in whenever a model is wired, so the URL resolves from any namespace. A caller hands it to a client library as its base URL and names values.model as its model; every other wired model is served at the same URL under its own alias as the model name. Empty while nothing is wired to the models socket.
modelstring—否The alias a consumer wired to the gateway sends as its model name: values.model. The gateway's route sends a request naming it to the model wired under that alias, asking for the model name that model publishes. Empty while nothing is wired to the models socket.
metrics_pod_selectorstring—否Kubernetes label selector matching this gateway's Envoy proxy pods, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path`.
metrics_pod_portstring—否Name of the container port on those pods that carries the metrics, `metrics`.
metrics_pathstring—否Path the metrics are served at on that port, `/stats/prometheus`.

uses 套接字

此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。

extension

选择器
gateway.aggrega.ai/extension-server=envoy-gateway
注入
—

此套接字未声明附加槽位,因此经由它的连接不携带任何附加项。

models

选择器
component.aggrega.ai/category=ai-model
注入
—

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
credentialfeature.aggrega.ai/kind=secret否—是Optional credential the gateway presents to the model this connection reaches, as a bearer token. When attached, the connection's backend security policy names the Secret the credential publishes, and the AI gateway controller reads the key from that Secret, in the gateway's namespace, under the data key apiKey, which the credential must publish: any other data key halts the build. The key appears in no rendered file. Unattached, the gateway adds no credential.

cache

选择器
datastore.aggrega.ai/engine=kv
注入
—

经由此套接字的每个连接可填充的槽位

槽位选择器必需注入敏感描述
credentialfeature.aggrega.ai/kind=secret否—是Optional password the gateway's rate-limit service presents to the Redis-protocol store this connection reaches. When attached, the Recipe hands the service a reference to the Secret the credential publishes, under the data key it publishes, and the service reads the password from that Secret in the gateway's namespace, so the password appears in no rendered file; a credential publishing no Secret name and data key halts the build. Unattached, the service connects with no password, which is what the shipped store components expect by default.
server_cafeature.aggrega.ai/kind=secret否file是Optional authority the gateway's rate-limit service checks the store's certificate against while the store publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt and sits in the gateway's namespace, where the service runs. The Recipe mounts the whole Secret into the service and points the service at the file. The build halts on a server_ca publishing no Secret name, and on one wired to a store served without TLS. Fill it with core/referenced-secret.

附加槽位

Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。

未声明附加槽位。

自注入允许列表

未声明自注入管道。

关系

与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。

使用

被使用

Component 概念参考 →

Aggrega 目录 — 收录组件、功能、配方以及渲染它们的插件的开放索引。

基于共享的 Aggrega 设计系统构建。

隐私