Component
core/ai-pipeline/temporal
Temporal, a durable-execution engine. A multi-step job is written as ordinary program code against one of the project's client libraries; the engine records every step's outcome as an event and hands the next piece of work to a worker the application itself deploys. Because the run is a replayable event history rather than a position in a process, a worker that crashes mid-job is replaced and the job resumes where it stopped, and a step that fails is retried on the policy the code declared. That division is what separates this from a scheduler: the engine owns the run's history and its timers, while the application owns the code each step executes. It keeps none of its own durable state. A relational datastore holds the event histories and a second database on that same connection holds the visibility index the console and the list APIs read, so the store is wired as a topology edge to a datastore component the Aggregate already declares rather than bundled inside this one. The engine is reached over gRPC on the frontend service, which is the address the provides contract publishes; a browser console is deployed alongside it. Realized on Kubernetes through a Helm Recipe that sources the project's own chart. It has no standalone local-container form, so no Compose Recipe is provided. Each of the engine's services serves its own metrics, in pods of its own, so the Recipe publishes the pod labels selecting every one of them, the name of their metrics port and the path, for a scraper that discovers those pods directly.
来歴
- コンテンツダイジェスト
- sha256:60d848e16a196199e572a931bf940dc5c539909ce68a5fb35ed51a0c51fa1881
- 公開日
- 2026-11-10T10:09:45Z
- 署名 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:b73cbac98a2f203410f5c676e05c155fa82c0f89872211a0655912026fe5d7fa
このバージョンの参照
oci://hub.aggrega.ai/component/core/ai-pipeline/temporal:1.0.0開発者パラメーター
開発者が Aggregate で設定する値です。
| 名前 | 型 | デフォルト | 必須 | 説明 |
|---|---|---|---|---|
| console_enabled | boolean | true | いいえ | Deploy the browser console beside the engine. The console reads the visibility index to list and inspect runs; the engine serves its gRPC API with or without it, so turning it off removes a browser surface rather than a capability. |
| admin_tools_enabled | boolean | true | いいえ | Deploy the administrative command-line image as a long-running pod an operator can exec into to inspect namespaces, describe a run, or apply a schema change. Turning it off removes that entry point; it serves no application traffic either way. |
運用担当者によるサイジング
運用担当者が環境ごとに調整するインフラストラクチャのサイジングです。
| 名前 | 型 | デフォルト | 必須 | 説明 |
|---|---|---|---|---|
| port | integer (min 1, max 65535) | 7233 | いいえ | Port the frontend service serves the gRPC API on. This is the address workers and clients dial, and the one the provides contract publishes. Most operators should omit this and let the Recipe assign the default (7233). |
| console_port | integer (min 1, max 65535) | 8080 | いいえ | Port the browser console listens on. It carries no application traffic; it exists so the console can be reached separately from the gRPC API. |
| history_shards | integer (min 1) | 512 | いいえ | How many shards the event history is partitioned across, which bounds how far the engine can scale out. It is fixed for the life of an installation — the engine cannot repartition an existing history, so raising it later requires a new installation. Size it for the load the installation is expected to reach rather than for its first day. |
| source_version | string | — | いいえ | Source artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility. |
| compute | object | — | いいえ | — |
| 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 engine's frontend. A worker or a client that starts a run points its connection target at this name together with `port`. |
| port | integer | — | はい | TCP port that frontend accepts client connections 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 — `grpc`, so a consumer configures one of the project's client libraries rather than an HTTP client. |
| metrics_pod_selector | string | — | いいえ | Kubernetes label selector matching the pods of every engine service, for a scraper that discovers those pods directly rather than scraping one address. Published beside `metrics_pod_port` and `metrics_path`. |
| metrics_pod_port | string | — | いいえ | Name of the container port on those pods that carries the metrics, `metrics`. |
| metrics_path | string | — | いいえ | Path the metrics are served at on that port, `/metrics`. |
uses ソケット
このコンポーネントが接続に用いる依存関係ソケットです。ソケットを介して配線される各接続のターゲットは、そのソケットのラベルセレクターを満たす必要があり、各接続はソケットが宣言するスロットにアタッチメントを持つことができます。必須スロットは、Aggregate または Release がそのソケットを介して配線する各接続が満たす必要があります。
metadata_store
- セレクター
- component.aggrega.ai/category=datastore
- 注入
- env
このソケットを介した各接続が埋めることのできるスロット
| スロット | セレクター | 必須 | 注入 | 機密 | 説明 |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | いいえ | — | はい | Password the engine authenticates to the relational datastore this connection reaches with. When attached, the Recipe points the engine at the produced Secret so the value never appears in the rendered manifest. Unattached, the engine is configured with no password, which suits a store reached without one and matches what the standard-library relational Recipes leave in place when nothing is attached to them. |
アタッチメントスロット
Feature がこのコンポーネントにアタッチされる、名前付きのバインディングポイントです。スロットのセレクターはどの Feature がそのスロットを埋められるかを制約し、その inject リストは Feature のマテリアルをどのように配信できるかを示します。必須スロットは、インスタンス上のアタッチメント、またはその上位のスコープでのアタッチメントによって、すべてのインスタンスでバインドされている必要があります。また、機密スロットは秘密のマテリアルを扱うものとして宣言されます。Feature は、どのスロットも宣言していない名前でアタッチすることもできます。
アタッチメントスロットは宣言されていません。
自己注入の許可リスト
env
関係
他の公開エンティティとの間の型付きエッジです。公開されたターゲットがない参照は、リンクではなく切れたエッジとして表示されます。
使用先
- 使用ソケット «metadata_store» を使用
component.aggrega.ai/category=datastore
アタッチメントスロット:credential
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 →
使用元
ソケット «upstream» を使用
ソケット «forward_target» を使用
ソケット «scrape_target» を使用
ソケット «store» を使用
適用対象
適用対象
適用対象
適用対象
適用対象
適用対象
適用対象
実装