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

Recipe

server

The generic long-running server primitive on Kubernetes via the helm provider's Workload synthesis: a Deployment plus a ClusterIP Service carrying inbound traffic to the container's port. The Service is what makes the operational type — compute that expects inbound application traffic — readable in the emitted bytes, and it is what separates this realization from the background-worker primitive's, which emits no Service at all. The component declares no developer fields of its own, so everything the workload needs comes from the operator: the image, the port, the replica count and the resource quantities. It needs no cluster control plane, so it carries no prerequisite affirmation and emits no custom resource. No provides contract is emitted, because the component declares none: this primitive publishes nothing across an edge. What reaches the container from the component's own edges is what each edge's inject block dictates, because the image is the Release's own code: env entries become variables and file entries read-only files, and an arg entry or any other delivery mechanism is refused by name. An edge that dictates nothing delivers nothing. The component's own inject block delivers env entries the same way. A credential attached to the component reaches the container the same way, through the delivery pipe: a core/secret-value attachment, its value written into the rendered Deployment, or a core/secret-provided one. A credential published for the pod to reference, such as core/referenced-secret or core/random-password, cannot reach it, because the component declares no credential slot a reference could name, so the build halts naming the attachment.

Versi

1.0.01.1.0

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:49d6b03bce57d640151f97afd0f4e1ebf1bffd350dc09e82b5be99fd98aeb4f5
Dipublikasikan
2026-11-10T10:27:08Z
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:dfd1ea4587d1ca943ff64d3f25251979c9f5a92692165e1ef8d078493b9d6970

Referensi pada versi ini

oci://hub.aggrega.ai/recipe/helm/server:1.0.0
Target
—
Mengimplementasikan
core/compute/server:1.0.0

Menyediakan

Templat pointer deterministik yang dihubungkan resep ini untuk konsumen.

Tidak ada templat provides yang dideklarasikan.

Workload

Workload · form: stateless · replicas: {{ · containers: main

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 Recipe →

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

Dibangun dengan sistem desain Aggrega yang digunakan bersama.

Privasi