Component
core/devtool/harbor
A Harbor container registry, declared as one component and deployed as one unit: an API and token-service control plane, an OCI blob store, a web console, an asynchronous worker tier, a vulnerability scanner, a relational backend and a key-value cache, so the registry stands up with nothing else declared beside it. An Aggregate declaring it gets a registry container clients log in to, push to and pull from, and a console to administer it, both behind the one in-cluster address `provides` publishes. Six keys and shared secrets have no default and the build halts until each slot is filled: token_key, the key the token service signs with and its certificate; core_secret, jobservice_secret and registry_http_secret, the secrets its services authenticate to each other and sign upload state with; csrf_key, the key the control plane signs request-forgery tokens with; and secret_key, the key it encrypts stored credentials with. Each is read from a Kubernetes Secret by name, so none reaches the rendered artifact. The passwords — the administrator's, in its slot, and the backend's and the blob store's account, in `infra` — take development values the Recipe states when left unattached and unset, for evaluation and development. Those values are published in this catalog: a Release serving real traffic replaces them. With `values.metrics_enabled` true the Recipe turns on the Prometheus metrics of the control plane, worker tier, blob store and exporter and publishes their four Services as `metrics_service`; false, those keys are empty. The switch also opens the blob store's debug listener — profiling, execution traces and runtime variables, no caller check — to every in-cluster caller.
출처
- 콘텐츠 다이제스트
- sha256:25d89a6d6fb7205d31f43b5b859b78b01d47f95942ca76a01d8ce8a2f6c9f39f
- 게시일
- 2026-11-10T10:11:34Z
- 서명 ID
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
서명
- 공식application/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:98cb969e18ee651a7aa4cf25df2d375fe6b2cabe65777885a693d68331a59f53
이 버전의 참조
oci://hub.aggrega.ai/component/core/devtool/harbor:1.0.0개발자 매개변수
개발자가 Aggregate에서 설정하는 값입니다.
| 이름 | 타입 | 기본값 | 필수 | 설명 |
|---|---|---|---|---|
| log_level | string | — | 아니요 | Log verbosity the registry's services run at (debug, info, warning, error or fatal). Omit to use the product's default (info). |
| metrics_enabled | boolean | false | 아니요 | Turns on the registry's own metrics, in the Prometheus format at /metrics on port 8001 of the control plane, the worker tier, the blob store and the exporter, puts that port on each one's Service, and publishes the four Services for a scraper to discover as `metrics_service`, beside `metrics_service_port` and `metrics_path`; while false those keys are empty. The same setting moves the blob store's debug listener from the pod's loopback address onto every interface and names its port on the blob store's Service, newly opening it to every in-cluster caller that reaches the pod. That listener checks no caller and, beside the metrics, serves /debug/pprof (CPU profiles and execution traces on request, heap and goroutine dumps, the command line) and /debug/vars (the command line, memory statistics and runtime counters); it has no route that changes the registry. The registry's chart offers no way to turn the metrics on without it. |
운영자 사이징
운영자가 환경별로 조정하는 인프라 사이징입니다.
| 이름 | 타입 | 기본값 | 필수 | 설명 |
|---|---|---|---|---|
| port | integer (min 1, max 65535) | 80 | 아니요 | Port the registry's single published address accepts traffic on. It sets the Service port only — the reverse proxy behind it listens on a port the product fixes — so any value in range is servable, including the privileged ports a registry is conventionally reached on. |
| external_base_url | string | — | 아니요 | Externally reachable address of the registry, as assembled at the ingress tier — scheme, host and, where it is not the scheme's default, port, with no path; for example https://registry.example.com. The registry composes from this the token-service address it returns to a container client that logs in, and the push and pull commands its console shows, so a client outside the cluster is sent somewhere it can reach. A container client addresses a registry at the root of a host, so the Recipe halts the build on an address carrying a path. Omitted, the Recipe gives the registry its in-cluster address, which is correct for a registry nobody reaches from outside the cluster. |
| engine_version | string | v2.15.2 | 아니요 | Harbor container image tag. The product ships every one of its service images on a single tag, so this one value selects them all. Moving it away from the Recipe's default is not guaranteed to match the chart the Recipe pulls; move source_version with it. |
| source_version | string | — | 아니요 | Version of the Helm chart the Recipe pulls. Changing it away from the Recipe's default does not guarantee value-mapping compatibility with the new chart. |
| compute | object | — | 아니요 | — |
| storage | object | — | 아니요 | — |
| database_password | string | — | 아니요 | Password for the account the control plane connects to its relational backend as. Left unset, helm/harbor-chart uses the development literal `apppass`, which this catalog publishes, so every Release that leaves it unset shares that password. |
| registry_username | string | harbor_registry_user | 아니요 | Account name the control plane and the worker tier present to the blob store. Set it together with registry_password and registry_htpasswd, or set none of the three. |
| registry_password | string | — | 아니요 | Password the control plane and the worker tier present to the blob store. Set it together with registry_username and registry_htpasswd, or set none of the three. Left unset, helm/harbor-chart uses the development literal `harbor_registry_password` and a development htpasswd line in place of registry_htpasswd, both published in this catalog, so every Release that leaves the three unset shares that account. |
| registry_htpasswd | string | — | 아니요 | The other two keys as a single htpasswd line — `<registry_username>:<bcrypt hash of registry_password>` — which is the form the blob store checks a presented account against. Produce it with `htpasswd -nbB <username> <password>`. Set it together with the other two, or set none of the three. |
| overrides | object (open) | — | 아니요 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
출력 계약
이 컴포넌트가 uses 토폴로지를 통해 소비자에게 게시하는 값입니다.
| 이름 | 타입 | 기본값 | 필수 | 설명 |
|---|---|---|---|---|
| host | string | — | 예 | In-cluster DNS name of the Service fronting the whole registry. A container client logs in, pushes and pulls against this name, and a browser reaches the console on it. |
| port | integer | — | 예 | TCP port that Service accepts traffic on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default. |
| protocol | string | — | 아니요 | How the published address is spoken to — `http`, so a consumer composes an address on that scheme. |
| metrics_service | string | — | 아니요 | Names of the Services the registry's metrics sit behind, comma-separated — the control plane's, the blob store's, the worker tier's and the exporter's, `<host>-core,<host>-registry,<host>-jobservice,<host>-exporter` where `<host>` is the published host — for a scraper that discovers each endpoint of those Services rather than scraping one address. Published beside `metrics_service_port` and `metrics_path` while values.metrics_enabled is true; empty otherwise. |
| metrics_service_port | string | — | 아니요 | Name of the port of each of those Services that carries the metrics, `http-metrics`. Set and empty together with `metrics_service`. |
| metrics_path | string | — | 아니요 | Path the metrics are served at on that port, `/metrics`. Set and empty together with `metrics_service`. |
uses 소켓
이 컴포넌트가 연결에 사용하는 의존성 소켓입니다. 소켓을 통해 배선되는 모든 연결의 대상은 해당 소켓의 레이블 셀렉터를 충족해야 하며, 각 연결은 소켓이 선언한 슬롯에 첨부를 전달할 수 있습니다. 필수 슬롯은 Aggregate 또는 Release가 해당 소켓을 통해 배선하는 각 연결이 채워야 합니다.
선언된 uses 소켓이 없습니다.
첨부 슬롯
Feature가 이 컴포넌트에 첨부되는 이름 있는 바인딩 지점입니다. 슬롯의 셀렉터는 어떤 Feature가 슬롯을 채울 수 있는지를 제한하고, 슬롯의 inject 목록은 Feature의 자료를 어떻게 전달할 수 있는지를 지정합니다. 필수 슬롯은 인스턴스의 첨부 또는 그 위 범위의 첨부를 통해 모든 인스턴스에서 바인딩되어야 하며, 민감 슬롯은 비밀 자료를 처리하도록 선언됩니다. Feature는 어떤 슬롯도 선언하지 않은 이름으로 첨부될 수도 있습니다.
| 슬롯 | 셀렉터 | 필수 | 주입 | 민감 | 설명 |
|---|---|---|---|---|---|
| token_key | feature.aggrega.ai/kind=secret | 예 | — | 예 | Required credential holding the RSA private key the registry's token service signs its tokens with, and the certificate over that key: a Kubernetes Secret carrying the PEM key under the data key tls.key and the PEM certificate under tls.crt, as a kubernetes.io/tls Secret does. The Recipe names that Secret, so the key never appears in the rendered artifact. There is no default: the build halts when nothing fills this slot, and when the credential filling it publishes no Secret name. |
| core_secret | feature.aggrega.ai/kind=secret | 예 | — | 예 | Required credential holding the shared secret the control plane, the worker tier and the blob store's controller authenticate to each other with: a Kubernetes Secret carrying it under the data key secret, exactly 16 characters. The Recipe names that Secret, so the secret never appears in the rendered artifact. There is no default: the build halts when nothing fills this slot, and when the credential filling it publishes no Secret name. |
| csrf_key | feature.aggrega.ai/kind=secret | 예 | — | 예 | Required credential holding the key the control plane signs its cross-site request forgery tokens with. It must be exactly 32 characters; a shorter or longer value is refused by the control plane at start-up. The Recipe names the Secret and the data key the credential publishes. There is no default: the build halts when nothing fills this slot, and when the credential filling it publishes no Secret name and data key. |
| secret_key | feature.aggrega.ai/kind=secret | 예 | — | 예 | Required credential holding the key the control plane encrypts stored credentials with — the credentials of the upstream registries it replicates from and to: a Kubernetes Secret carrying it under the data key secretKey, exactly 16 characters. Changing it on a registry that already holds replication credentials makes those credentials unreadable, so it is set once, when the registry is first stood up. The Recipe names that Secret, so the key never appears in the rendered artifact. There is no default: the build halts when nothing fills this slot, and when the credential filling it publishes no Secret name. |
| jobservice_secret | feature.aggrega.ai/kind=secret | 예 | — | 예 | Required credential holding the shared secret the worker tier and the control plane authenticate to each other with, 16 characters as the registry's Helm chart documents it. The Recipe names the Secret and the data key the credential publishes, so the secret never appears in the rendered artifact. There is no default: the build halts when nothing fills this slot, and when the credential filling it publishes no Secret name and data key. |
| registry_http_secret | feature.aggrega.ai/kind=secret | 예 | — | 예 | Required credential holding the secret the blob store signs its upload state with, which every replica of the blob store must share, 16 characters as the registry's Helm chart documents it. The Recipe names the Secret and the data key the credential publishes, so the secret never appears in the rendered artifact. There is no default: the build halts when nothing fills this slot, and when the credential filling it publishes no Secret name and data key. |
| admin_password | feature.aggrega.ai/kind=secret | 아니요 | — | 예 | Optional credential for the registry's built-in administrator account, the account the web console and the API are first administered through. Unattached, helm/harbor-chart sets its password to the development literal `Harbor12345`, which this catalog publishes, so every Release that leaves the slot unattached shares that password. |
자체 주입 허용 목록
선언된 자체 주입 파이프가 없습니다.
관계
게시된 다른 엔터티와 주고받는 타입 지정 에지입니다. 게시된 대상이 없는 참조는 링크가 아닌 끊어진 에지로 표시됩니다.
사용함
이 엔터티는 카탈로그의 어떤 것도 사용하지 않습니다.
사용됨
소켓 «backend» 사용
소켓 «databases» 사용
소켓 «etcd» 사용
소켓 «backend» 사용
소켓 «backend» 사용
소켓 «forward_target» 사용
소켓 «scrape_target» 사용
소켓 «backend» 사용
소켓 «database» 사용
적용 대상
적용 대상
적용 대상
구현