Halaman ini diterjemahkan oleh mesin. Baca versi asli dalam bahasa Inggris.

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.

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:9a6e8f75457da9c3cdc41ebb5a79bb47b1343e839e4a18b037b2c4a8366882cc
Dipublikasikan
2026-11-10T10:15:39Z
Identitas penandatangan
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Tanda tangan

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

Referensi pada versi ini

oci://hub.aggrega.ai/featurerecipe/helm/http-route:1.0.0
Target
—
Mengimplementasikan
core/http-route:1.0.0

Menyediakan

Templat pointer deterministik yang dihubungkan resep ini untuk konsumen.

Tidak ada templat provides yang dideklarasikan.

Workload

Tidak ada templat beban kerja yang dideklarasikan.

Nilai lokal

Tidak ada nilai lokal yang dideklarasikan.

Pemetaan values

Tidak ada pemetaan values yang dideklarasikan.

Relasi

Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.

Menggunakan

Digunakan oleh

Tidak ada apa pun di katalog yang bergantung pada entitas ini.

Referensi konsep FeatureRecipe →

Katalog Aggrega — indeks terbuka berisi komponen, fitur, resep, dan plugin yang merendernya.

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi