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

Component

core/ai-model/litellm

LiteLLM running in-cluster as a self-hosted, OpenAI-compatible model proxy. The published alias in values.model is the name the proxy serves under, and it forwards each request to the provider-qualified upstream model in values.upstream_model, so a consumer reaches one stable in-cluster endpoint and name while the target behind it changes independently. The proxy holds the upstream credential attached to its provider_key slot and presents it on a caller's behalf. Exports its host, port, endpoint, model and protocol, the contract every other model component publishes. Because it holds that credential, its Recipes forward only the request fields the proxy declares for the route, plus any the Release admits through infra.admitted_request_fields, and refuse the rest with an error naming the field. They answer only the model routes, the model listing, the health checks and key management, and refuse every other path, so its token-count, pass-through and other administrative routes, its console and model paths carrying the model name are not available through any. On Kubernetes, reach for helm/litellm, which synthesizes the proxy, where the build must fetch nothing, and for helm/litellm-chart, BerriAI's chart, where its registry is reachable; for local development, the compose Recipe. With `values.metrics_enabled` true each Recipe has the proxy serve its Prometheus metrics, its path allowlist forwarding a GET of /metrics alone to them from port 9090, and publishes that address as `metrics_endpoint`; false, that key is empty. The port checks no caller, and the metrics name the hashed keys, key aliases and user emails the proxy attributes spend to.

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:c9e4f18a552bb4bfccc17282661ddd96f87aca6478c7f7a0dddcdda6a35a93b4
发布时间
2026-11-10T10:09:16Z
签名身份
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:d6b38e6c33e02b29347f6d8447b229b897aedadd5cec8c00546dc926d8187ea1

此版本的引用

oci://hub.aggrega.ai/component/core/ai-model/litellm:1.0.0

开发者参数

开发者在 Aggregate 中设置的值。

扩展 BaseComponents#/schemas/BaseModelParameter

名称类型默认值必需描述
upstream_modelstring—是The provider-qualified upstream model the proxy forwards to, in the proxy's own provider/model notation (for example openai/gpt-4o or anthropic/claude-sonnet-4). A deterministic pointer string the runtime resolves per request; the compiler never contacts the provider.
provider_key_variablestringOPENAI_API_KEY否Name of the environment variable under which the upstream provider's credential is delivered, and the variable the proxy's configuration names in its place. The correct name follows the provider chosen in upstream_model — the default suits an OpenAI-notation target; an Anthropic target uses ANTHROPIC_API_KEY, and so on per the provider's own convention.
metrics_enabledbooleanfalse否Has the proxy serve its own Prometheus metrics through its path allowlist on port 9090, where a GET of /metrics alone is forwarded, and publishes their address as `metrics_endpoint`; while false that key is empty. The port checks no caller, and the metrics name the hashed keys, key aliases and user emails the proxy attributes spend to, so anything that reaches the port reads them.

运维规格

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

扩展 LiteLLMGuardSchemas#/schemas/RequestGuardInfra

名称类型默认值必需描述
portinteger (min 1024, max 65535)4000否Server listen port for the proxy API. Most operators should omit this and let the Recipe assign the default (4000).
external_base_urlstring—否Externally reachable origin of the proxy, as assembled at the ingress tier — scheme, host and, where it is not the scheme's default, port, with no path; for example https://llm.example.com. The proxy composes from this the sign-in callback address it hands an identity provider, the address of its admin console it sends a browser to after sign-in, and the proxy address it writes into every alert it sends. The product documents this setting as an origin only, so the Recipes halt the build on an address carrying a path. Omitted, the proxy composes each of those addresses from the request that arrives, which is correct for a proxy nobody signs in to from outside the cluster.
engine_versionstringv1.103.1否LiteLLM proxy image tag. Selects the image tag of the proxy container on every Recipe.
source_versionstring—否Version of BerriAI's litellm-helm chart the chart-backed Recipe pulls, defaulting to the version that Recipe was checked against. The workload-synthesis and compose Recipes pull no chart and read nothing here.
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 fronting the proxy. A consumer that composes its own address dials this name; one that does not reads `endpoint` instead.
portinteger—是TCP port that Service accepts proxy requests on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
endpointstring—是Full base URL of the OpenAI-compatible API the proxy serves, with the host, the port and the API path already composed. A consumer hands it to a client library as its base URL.
modelstring—是Name a request must ask the proxy for. The proxy maps it onto whichever upstream provider it is configured to forward to, so a consumer names this rather than an upstream model.
protocolstring—否URL scheme to reach `host` and `port` over, for a consumer composing its own address rather than reading `endpoint`.
metrics_endpointstring—否The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:9090/metrics`, the host being the name of the Service the Recipe serves them on. Empty while values.metrics_enabled is false.

uses 套接字

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

未声明 uses 套接字。

附加槽位

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

槽位选择器必需注入敏感描述
api_keyfeature.aggrega.ai/kind=secret否env是Optional administrative key guarding the proxy's own API, which LiteLLM calls its master key. When attached, the Recipe delivers it as LITELLM_MASTER_KEY, the environment variable the proxy reads at startup, so callers and the management API must present it. Unlike a server that checks one key, the proxy also accepts the keys it issues through its key-management API and keeps in its bookkeeping database: with database_url attached a caller may present such a key instead, and with none the proxy accepts this key alone. Unattached, the proxy starts with no administrative key and treats every caller as an unprivileged internal user, which suits a development Release and not a shared one.
provider_keyfeature.aggrega.ai/kind=secret否env是Optional credential the proxy presents to the upstream provider it routes to, delivered as the environment variable named in values.provider_key_variable. Unattached, the proxy runs and serves its API but holds no upstream credential, so a routed request fails at the provider; attach one for any Release that must actually reach a model.
database_urlfeature.aggrega.ai/kind=secret否env是Optional connection string for the proxy's own bookkeeping database, which backs key management, spend tracking and request logs. When attached, the Recipe delivers it as DATABASE_URL, the environment variable the proxy reads at startup — on helm referenced from the secret that holds it, so the proxy's Deployment carries the reference and never the string; on compose as the value its credential delivers under that name, which a Compose variable reference keeps out of the file. The compiler never connects to the database. Unattached, the proxy runs stateless — it serves and routes normally, and the features that need persistence are simply inactive.

自注入允许列表

env

关系

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

使用

被使用

Component 概念参考 →

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

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

隐私