Component
core/gateway/higress
Higress, an open-source gateway built on Envoy and configured through Kubernetes resources: its routes are ingresses, the services it reaches are its own registry's entries, and its controls are WebAssembly plugins on the routes they act on. It terminates client HTTP on its proxy port, publishing its host, port and protocol. It serves models: each model wired to its models socket is reached under an alias at /<alias>/v1 through Higress's AI proxy, sent to the endpoint and model name the model publishes, presenting the connection's credential from its Secret; over https it checks that the model's certificate chains to the system's trust anchors and names its host. Connections naming one alias in serves share its requests. It publishes the route of values.model as its endpoint and that alias as its model, so an agent's model socket takes it in place of a model; with nothing wired both are empty. On those routes it masks requests, keeps a token budget in its cache socket's store, records each model request in its access log and sets each route's retry, refusing by name what Higress cannot keep; it declares no callers. Reply validation, the fallback chain, the semantic cache, the prompt-injection shield and latency-based target selection halt the build naming what Higress lacks. It pulls its plugin modules from Higress's plugin registry at run time, which the cluster must reach and the build cannot check. It is realized on Kubernetes by `higress-chart` alone, and publishes the pod label, port name and path a scraper discovers its gateway's metrics by.
来源
- 内容摘要
- sha256:8b92c8a380a01667259d0b041b43a42dc1c93b50b58b21741d1cc4a57a8260f9
- 发布时间
- 2026-11-10T10:11:55Z
- 签名身份
- 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:ef9dfa3941c48639070a7b9379a7ff22eb5637b82b98304936be0d1c243fd7b7
此版本的引用
oci://hub.aggrega.ai/component/core/gateway/higress:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| model | string | — | 否 | The alias this gateway publishes as its model, and whose route its published endpoint addresses — a serves value a models connection names, or the name of a connection naming none. It must be an alias the models socket serves, and the build halts naming this value otherwise; it is required while the models socket holds a connection, and omitted while it holds none. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| http_port | integer (min 1, max 65535) | 80 | 否 | Proxy data-plane port consumers connect to. |
| source_version | string | — | 否 | Version of the Higress chart the chart-backed realization pulls. The realization holds the chart versions its configuration is proven at, and the build halts naming them on any other. |
| compute | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | In-cluster DNS name of the Service fronting the gateway's proxy, the name alone without a namespace. A consumer sends its client traffic here rather than to the service behind the gateway. |
| port | integer | — | 是 | TCP port that Service accepts proxied traffic on, infra.http_port. |
| protocol | string | — | 否 | How the published address is spoken to — `http`, so a consumer composes an address on that scheme. |
| endpoint | string | — | 否 | Full base URL of the OpenAI-compatible API the gateway serves for the alias values.model names, with the host, the port and that alias's route already composed. A caller hands it to a client library as its base URL. Every other alias is served at the same host and port under its own name in the path. Empty while nothing is wired to the models socket. |
| model | string | — | 否 | The alias a consumer wired to the gateway sends as its model name: values.model. The route behind the endpoint asks each model for the name that model publishes, whatever name a request carries. Empty while nothing is wired to the models socket. |
| metrics_pod_selector | string | — | 否 | Kubernetes label selector matching the gateway's pods, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path`. |
| metrics_pod_port | string | — | 否 | Name of the container port on those pods that carries the metrics, `istio-prom`. |
| metrics_path | string | — | 否 | Path the metrics are served at on that port, `/stats/prometheus`. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
models
- 选择器
- component.aggrega.ai/category=ai-model
- 注入
- —
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | 否 | — | 是 | Optional credential the gateway presents to the model this connection reaches, as a bearer token. When attached, the AI proxy's configuration names the Secret the credential publishes and the data key holding the key there, and the Higress controller reads the key from that Secret, in the gateway's namespace, so the key appears in no rendered file. The credential must publish both, and a Secret name holding a dot halts the build, because Higress reads the name up to its first dot; a realization naming its own Secret after the connection and this slot writes such a dot, so realize it with one naming an existing Secret whose name holds none. Unattached, the gateway adds no credential. |
cache
- 选择器
- datastore.aggrega.ai/engine=kv
- 注入
- —
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | 否 | — | 是 | Optional password the gateway's token budget presents to the Redis-protocol store this connection reaches. When attached, the budget's configuration names the Secret the credential publishes and the data key holding the password there, and the Higress controller reads the password from that Secret, in the gateway's namespace, so it appears in no rendered file. The credential must publish both, and a Secret name holding a dot halts the build, because Higress reads the name up to its first dot; realize it with one naming an existing Secret whose name holds none. Unattached, the plugin connects with no password, which is what the shipped store components expect by default. |
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
未声明自注入管道。
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 使用使用套接字 «models»
component.aggrega.ai/category=ai-model
附加槽位:credential
core/ai-model/ai21 v1.0.0 →core/ai-model/anthropic v1.0.0 →core/ai-model/azure-managed v1.0.0 →core/ai-model/azure-openai v1.0.0 →core/ai-model/azure-openai-embedding v1.0.0 →core/ai-model/bedrock v1.0.0 →core/ai-model/bedrock-embedding v1.0.0 →core/ai-model/cohere v1.0.0 →core/ai-model/databricks v1.0.0 →core/ai-model/docker-model-runner v1.0.0 →core/ai-model/gemini v1.0.0 →core/ai-model/huggingface v1.0.0 →core/ai-model/litellm v1.0.0 →core/ai-model/mistral v1.0.0 →core/ai-model/nemoguard-content-safety v1.0.0 →core/ai-model/nvidia-api v1.0.0 →core/ai-model/nvidia-nim v1.0.0 →core/ai-model/nvidia-nim-operator v1.0.0 →core/ai-model/ollama v1.0.0 →core/ai-model/openai v1.0.0 →core/ai-model/openai-compatible v1.0.0 →core/ai-model/openai-embedding v1.0.0 →core/ai-model/replicate v1.0.0 →core/ai-model/sagemaker v1.0.0 →core/ai-model/tei v1.0.0 →core/ai-model/tgi v1.0.0 →core/ai-model/vertex-ai v1.0.0 →core/ai-model/vertex-ai-embedding v1.0.0 →core/ai-model/vllm v1.0.0 → - 使用使用套接字 «cache»
datastore.aggrega.ai/engine=kv
附加槽位:credential
被使用
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «model»
使用套接字 «target_model»
使用套接字 «extraction_model»
使用套接字 «embedding_model»
使用套接字 «upstream»
使用套接字 «forward_target»
使用套接字 «scrape_target»
使用套接字 «store»
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
适用于
实现