Esta página se tradujo automáticamente. Leer el original en inglés.

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.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:4da58394f29dd03b0279de9c8a55207c1db5df5424964c9ae5d8095f619dde67
Publicado
2026-11-10T10:25:54Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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

Referencia en esta versión

oci://hub.aggrega.ai/recipe/helm/nginx:1.0.0
Destino
—
Implementa
core/gateway/nginx:1.0.0

Proporciona

Plantillas de punteros deterministas que esta receta cablea para los consumidores.

NombrePlantilla
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
protocolhttp

Workload

Workload · replicas: 1 · containers: main

Variables locales

NombrePlantilla
upstream_host_variableNGINX_UPSTREAM_HOST
upstream_port_variableNGINX_UPSTREAM_PORT

Mapeo de valores

No se declaró ningún mapeo de valores.

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

  • implementaimplementacontrato compatible

    core/gateway/nginx:1.0.0

    Todas las salidas obligatorias se satisfacen y cada salida proporcionada está nombrada en el contrato.

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto Recipe →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad