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

Recipe

nginx

NGINX reverse-proxy gateway on Kubernetes via the helm provider's Workload synthesis, running the official upstream nginx image (no external Helm chart). NGINX holds no persistent state, so it renders a stateless Deployment plus a ClusterIP Service and declares no storage. The upstream host and port arrive on .context.inject.env under the two variables the locals name, which the `upstream` edge's inject block names, and are written into a minimal NGINX server configuration whose proxy_pass forwards matching requests to that upstream; the config is written at container start and nginx is then started in the foreground. With an edge wired on any socket but guard and either variable missing from the pipe, the build halts naming the edge and its socket; with neither on the pipe and no such edge, the location answers 503. A core/prompt-injection-shield attachment's realization (prompt-injection-shield-nginx) writes the two variables with the address of the guard wired to the guard socket. Each core/traffic-shadowing attachment adds a mirror to that location: an upstream group naming the Service the attachment's infra names, and an internal location sending a copy of every forwarded request there with its original URI, whose response NGINX discards. NGINX copies every request it forwards and cannot copy a share of them, so the FeatureRecipe realizing the attachment (traffic-shadowing-nginx) halts on a share below 100, and this Recipe halts on an attachment to a gateway that forwards nothing. Each core/concurrency-limit attachment adds a cap, one total across NGINX's worker processes, and a request past it is answered 503; concurrency-limit-nginx refuses scope model.

来源

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

此版本的引用

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

提供

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

名称模板
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
protocolhttp

Workload

Workload · replicas: 1 · containers: main

局部变量

名称模板
upstream_host_variableNGINX_UPSTREAM_HOST
upstream_port_variableNGINX_UPSTREAM_PORT

值映射

未声明值映射。

关系

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

使用

  • 实现实现契约兼容

    core/gateway/nginx:1.0.0

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

被使用

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

Recipe 概念参考 →

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

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

隐私