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

FeatureRecipe

http-route

Component-scope FeatureRecipe for core/http-route: emits one Gateway API HTTPRoute per attached component from a co-located chart, attaching the route to the gateway the Operator names and forwarding the host the operator names (infra.host) and the path the developer writes (values.path) to a port on the Service the component's own Recipe emits. Resource Generation via source + valuesMapping; the per-component .context.* root is available at component scope. The route is emitted at gateway.networking.k8s.io/v1, which is the version the routing API both serves and stores it at. The backend Service name is the operator-set service_name where one is supplied, and otherwise the primary Service a synthesized workload emits for the attached component — the component's rendered name followed by the primary service key, which is how workload synthesis names it. The emitted resource is named for the component that carries the attachment, by the same rendered name — the name the helm provider spells in the characters a Kubernetes name allows — and for the attachment itself, so one component carrying two of these attachments emits two routes rather than one overwriting the other. A gateway control plane is a runtime prerequisite: the build halts unless the Operator affirms one is running in the target cluster (infra.control_plane_present), so a route is never emitted into a cluster with nothing to reconcile it into routing. The build also halts where the attachment names no gateway to attach to or no Service port to forward to, because neither has a fallback that could be right.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:9a6e8f75457da9c3cdc41ebb5a79bb47b1343e839e4a18b037b2c4a8366882cc
Publicado
2026-11-10T10:15:39Z
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:5a3af056df240cdcce6b98447e3a826c9b2eb1e149a27091bcb66f36d9c3a7b5

Referencia en esta versión

oci://hub.aggrega.ai/featurerecipe/helm/http-route:1.0.0
Destino
—
Implementa
core/http-route:1.0.0

Proporciona

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

No se declararon plantillas provides.

Workload

No se declaró ninguna plantilla de carga de trabajo.

Variables locales

No se declararon variables locales.

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

Usado por

Nada en el catálogo depende de esta entidad.

Referencia del concepto FeatureRecipe →

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