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

Recipe

harbor-chart

A Harbor container registry on Kubernetes via the product's own Helm chart, served from its project's HTTPS chart repository. The chart deploys the whole registry as one unit, in the order its services need, with the wiring the product's own maintainers keep in step with it. Its Ingress and transport security are left switched off, and the reverse proxy is published as one cluster-internal Service. `values.metrics_enabled` turns the chart's metrics on and publishes the four Services serving them. The same chart setting opens the blob store's debug listener — profiling, execution traces and runtime variables, with no caller check — to every in-cluster caller. Every image the chart runs is pinned to a resolvable release tag — one tag, which infra.engine_version selects for all of them — and the chart version is pinned in source.version. Every secret the chart would otherwise generate at render time is supplied instead, so the output is byte-identical across renders: the token-signing key and its certificate, the services' three shared secrets, the request-forgery key and the key stored credentials are encrypted with always from the attached credential by name, the administrator's password by name where attached, and every password the Release leaves unset from a fixed development value. No key is written into the rendered artifact. The address the registry reports as its own — the token-service address it returns to a container client and the commands its console shows — is the chart's `externalURL`: `infra.external_base_url` when set, and the build halts when that address carries a path; unset, the published in-cluster Service address.

Asal-usul

ResmiDitandatangani oleh identitas penandatangan yang diakui katalog ini sebagai penerbit resmi.
Digest konten
sha256:451177812a49719bb64558ea013b6b234198f3f4ed07cfdaadcabfe9033986f7
Dipublikasikan
2026-11-10T10:24:12Z
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:233e686bdeb743a96717f7c4cbfab8e0fadaa5486cf67f5852a6429121392705

Referensi pada versi ini

oci://hub.aggrega.ai/recipe/helm/harbor-chart:1.0.0
Target
—
Mengimplementasikan
core/devtool/harbor:1.0.0

Menyediakan

Templat pointer deterministik yang dihubungkan resep ini untuk konsumen.

NamaTemplat
host{{ .context.rendered_name }}
port{{ .infra.port }}
protocolhttp
metrics_service{{ if .values.metrics_enabled }}{{ .context.rendered_name }}-core,{{ .context.rendered_name }}-registry,{{ .context.rendered_name }}-jobservice,{{ .context.rendered_name }}-exporter{{ end }}
metrics_service_port{{ if .values.metrics_enabled }}http-metrics{{ end }}
metrics_path{{ if .values.metrics_enabled }}/metrics{{ end }}

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

  • mengimplementasikanmengimplementasikankontrak kompatibel

    core/devtool/harbor:1.0.0

    Semua keluaran wajib terpenuhi dan setiap keluaran yang disediakan disebutkan dalam kontrak.

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