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

Recipe

apisix-chart

Apache APISIX on Kubernetes via the project's own Helm chart, its bundled etcd and ingress controller switched off: a Deployment, a ClusterIP Service for the proxy data plane and the configuration map the gateway reads. With nothing wired to the models socket the configuration store is the etcd component wired on the `etcd` socket, and a ClusterIP Service fronts the Admin API, authenticated by the key the `admin_key` slot names: the chart reads it from the Secret the attached credential publishes, so no rendered file carries a key. Its client allowlist, `apisix.admin.allow.ipList`, admits every address, so narrow it wherever the admin port is routable from outside the cluster. With a model wired the chart runs in its standalone mode: each connection's routes, through APISIX's AI proxy, sit in a ConfigMap named after the gateway, which reads them with no etcd and no Admin API. A connection's credential, and each key of the callers infra.callers declares, arrives as an env secretKeyRef the routes file names through APISIX's $env:// reference, so no key is in the rendered output; each caller is a consumer whose key every route checks. Written onto the routes: core/period-budget as token rate limiting, with one replica; core/semantic-caching as a semantic cache; core/prompt-deny-patterns as a prompt guard — no completion route beside the budget or the guard. With `values.metrics_enabled` true, the chart serves the gateway's metrics on its own Service, port 9091, which checks no caller, published as provides.metrics_endpoint; false, that key is empty. Reach for it where a chart repository is reachable at build time or a model is served, and for `apisix` where the build must fetch nothing.

来源

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

此版本的引用

oci://hub.aggrega.ai/recipe/helm/apisix-chart:1.0.0
目标
—
实现
core/gateway/apisix:1.0.0

提供

此配方为使用方接入的确定性指针模板。

名称模板
host{{ .context.rendered_name }}-gateway
port{{ .infra.http_port }}
protocolhttp
endpoint{{ with optional .values "model" "" }}http://{{ $.context.rendered_name }}-gateway:{{ $.infra.http_port }}/{{ . }}/v1{{ end }}
model{{ optional .values "model" "" }}
metrics_endpoint{{ if .values.metrics_enabled }}http://{{ .context.rendered_name }}-prometheus-metrics:9091/apisix/prometheus/metrics{{ end }}

Workload

未声明工作负载模板。

局部变量

名称模板
model_routes_config_map_suffix-model-routes
connection_variable_prefixAI_PROXY_
credential_variable_suffix_API_KEY
header_variable_suffix_AUTHORIZATION
caller_variable_prefixCALLER_
caller_key_variable_suffix_KEY
cache_store_password_variableCACHE_STORE_PASSWORD
callers{{ with optional .infra "callers" "" }}{{ range $i, $caller := . }}{{ if $i }}, {{ end }}{{ $caller }}{{ end }}{{ end }}

值映射

未声明值映射。

关系

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

使用

  • 实现实现契约兼容

    core/gateway/apisix:1.0.0

    所有必需输出均已满足,且提供的每个输出都在契约中列出。

被使用

目录中没有任何内容依赖此实体。

Recipe 概念参考 →

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

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

隐私