Esta página se tradujo automáticamente. Leer el original en 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.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:187235d759e07524d599fff750f4060a1cda6af66f38a3774bfeecfb1430b39c
Publicado
2026-11-10T10:22:08Z
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:91e316b9b40812cef7756de6b9c18bed385123977e2e32df63957e9037f6514d

Referencia en esta versión

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

Proporciona

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

NombrePlantilla
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

Variables locales

NombrePlantilla
admin_key_variableAPISIX_ADMIN_KEY

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/apisix: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