Esta página foi traduzida automaticamente. Ler o original em inglês.

Recipe

apisix

Apache APISIX on Kubernetes via the helm provider's Workload synthesis (a stateless Deployment plus a ClusterIP Service on the proxy port), running the official upstream image with no Helm chart. APISIX holds no local state — the etcd store is the system of record — so it renders stateless. The Admin API is reachable only from inside the cluster — no Service publishes its port — and is authenticated by the key the `admin_key` credential slot names, which the Deployment delivers from the Secret the attached credential publishes, so no rendered file carries the key. Its client allowlist, `allow_admin`, admits every address, so narrow it wherever the admin port is routable from outside the cluster. It renders no route: routes live in etcd, written through the Admin API at run time, so it serves no model, publishes an empty endpoint and model, and halts on a connection to the models socket — `apisix-chart` serves those. At its default image, APISIX 3.17.0, the gateway has no semantic cache plugin (`ai-cache`), and its token rate limiting counts per node; it halts on a core/period-budget, core/semantic-caching or core/prompt-deny-patterns attachment, and on infra.callers, which only a routes file declares. With `values.metrics_enabled` true, the gateway's metrics server moves off the loopback address and its port, 9091, which checks no caller, joins the Service, its address published as provides.metrics_endpoint; false, that key is empty. Reach for this realization where the build must complete with nothing fetched; reach for `apisix-chart`, which renders the project's own chart from named settings, where the configuration is expected to follow the product or a model is served.

Proveniência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como editor oficial.
Digest do conteúdo
sha256:187235d759e07524d599fff750f4060a1cda6af66f38a3774bfeecfb1430b39c
Publicado
2026-11-10T10:22:08Z
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:91e316b9b40812cef7756de6b9c18bed385123977e2e32df63957e9037f6514d

Referência nesta versão

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

Fornece

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

NomeModelo
host{{ .context.rendered_name }}-default
port{{ .infra.http_port }}
protocolhttp
endpoint
model
metrics_endpoint{{ if .values.metrics_enabled }}http://{{ .context.rendered_name }}-default:9091/apisix/prometheus/metrics{{ end }}

Workload

Workload · replicas: 1 · containers: main

Variáveis locais

NomeModelo
admin_key_variableAPISIX_ADMIN_KEY

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é apresentada como uma aresta quebrada em vez de uma ligação.

Usa

  • implementaimplementacontrato compatível

    core/gateway/apisix:1.0.0

    Todas as saídas obrigatórias são satisfeitas 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 partilhado do Aggrega.

Privacidade