Esta página foi traduzida automaticamente. Ler o original em inglês.

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.

Proveniência

OficialAssinado por uma identidade de assinatura que este catálogo reconhece como editor oficial.
Digest do conteúdo
sha256:451177812a49719bb64558ea013b6b234198f3f4ed07cfdaadcabfe9033986f7
Publicado
2026-11-10T10:24:12Z
Identidade de assinatura
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Assinatura

  • 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:233e686bdeb743a96717f7c4cbfab8e0fadaa5486cf67f5852a6429121392705

Referência nesta versão

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

Fornece

Modelos de ponteiros determinísticos que esta receita liga para os consumidores.

NomeModelo
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

Nenhum modelo de carga de trabalho declarado.

Variáveis locais

Nenhuma variável local declarada.

Mapeamento de valores

Nenhum mapeamento de valores declarado.

Relações

Arestas tipadas de e para outras entidades publicadas. Uma referência sem destino publicado é apresentada como uma aresta quebrada em vez de uma ligação.

Usa

  • implementaimplementacontrato compatível

    core/devtool/harbor:1.0.0

    Todas as saídas obrigatórias são satisfeitas e cada saída fornecida é nomeada no contrato.

Usado por

Nada no catálogo depende desta entidade.

Referência do conceito Recipe →

O catálogo Aggrega — um índice aberto de componentes, funcionalidades, receitas e dos plugins que os renderizam.

Criado com o sistema de design partilhado do Aggrega.

Privacidade