Esta página foi traduzida automaticamente. Leia o original em 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.

Procedência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como publicador oficial.
Digest do conteúdo
sha256:4da58394f29dd03b0279de9c8a55207c1db5df5424964c9ae5d8095f619dde67
Publicado
2026-11-10T10:25:54Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • 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

Referência nesta versão

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

Fornece

Modelos de ponteiros determinísticos que esta receita liga para os consumidores.

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

Workload

Workload · replicas: 1 · containers: main

Variáveis locais

NomeModelo
upstream_host_variableNGINX_UPSTREAM_HOST
upstream_port_variableNGINX_UPSTREAM_PORT

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é exibida como uma aresta quebrada em vez de um link.

Usa

  • implementaimplementacontrato compatível

    core/gateway/nginx:1.0.0

    Todas as saídas obrigatórias são atendidas e cada saída fornecida é nomeada no contrato.

Usado por

Nada no catálogo depende desta entidade.

Referência do conceito Recipe →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design compartilhado do Aggrega.

Privacidade