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

Recipe

kong-chart

Kong, a database-backed API gateway, on Kubernetes via the official Kong Helm chart, served from that project's HTTPS chart repository. The gateway's configuration lives in the PostgreSQL backend wired on the `backend` uses-socket, so the chart's bundled database, ingress controller and manager console are switched off. It renders a Deployment, a ServiceAccount, ClusterIP Services for the proxy data plane and the in-cluster Admin API, the chart's Kong custom-resource definitions, and the three schema-migration Jobs the product's maintainers sequence around a release: a bootstrap, an up-migration before an upgrade and a finishing migration after one. Reach for this realization where a chart repository is reachable at build time and the gateway will be upgraded in place; reach for `kong`, the workload-synthesis realization, where the build must complete with nothing fetched. Each model wired to the models socket gets a chat and a completion route through Kong's AI proxy, in a ConfigMap beside the chart that an init container imports into the database, retried on a first install until the bootstrap Job provisions the schema. A connection's credential arrives as an env secretKeyRef the routes name through Kong's environment vault, so no credential value is in the rendered output. With `values.metrics_enabled` true a ClusterIP Service, `<rendered_name>-status`, carries the chart's status port, 8100, and provides.metrics_endpoint publishes /metrics on it; false, neither. That port, open on the pod for the probes, answers only a GET of /status, /status/ready or /metrics from another address: the KongStatusGuard bundle refuses the rest, POST /status/ready among them.

来源

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

此版本的引用

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

提供

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

名称模板
host{{ .context.rendered_name }}-proxy
port{{ .infra.proxy_port }}
protocolhttp
endpoint{{ with optional .values "model" "" }}http://{{ $.context.rendered_name }}-proxy:{{ $.infra.proxy_port }}/{{ . }}/v1{{ end }}
model{{ optional .values "model" "" }}
metrics_endpoint{{ if .values.metrics_enabled }}http://{{ .context.rendered_name }}-status:{{ .locals.status_port }}/metrics{{ end }}

Workload

未声明工作负载模板。

局部变量

名称模板
model_routes_deliveryconfig_map
model_routes_filemodel-routes.yaml
model_routes_config_map_suffix-model-routes
connection_variable_prefixAI_PROXY_
credential_variable_suffix_API_KEY
header_variable_suffix_AUTHORIZATION
status_port8100
status_guard_deliveryconfig_map
status_guard_filestatus-guard.conf
status_guard_config_map_suffix-status-guard
status_guard_default_namespacedefault

值映射

未声明值映射。

关系

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

使用

  • 实现实现契约兼容

    core/gateway/kong:1.0.0

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

被使用

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

Recipe 概念参考 →

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

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

隐私