本页面为机器翻译。阅读英文原文。

Component

core/ai-pipeline/argo-workflows

Argo Workflows, a workflow engine for Kubernetes. A run is submitted as a Workflow custom resource naming the steps to take and how they depend on one another; the workflow controller watches those resources and reconciles each one, starting a pod per step, retrying a step that fails, fanning a step out over a list of inputs, and recording each step's outputs so a later step can read them. The cluster's own API holds the run, so the engine keeps no separate run database. An API server is deployed alongside the controller and serves the submission and query API and the web console; consumers reach it through the provides contract. Argo Workflows is 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. With `values.metrics_enabled` true the Recipe serves the workflow controller's metrics, at /metrics, over plain HTTP on a ClusterIP Service of their own, and publishes that address as `metrics_endpoint`; false, that key is empty. The port checks no caller.

来源

官方由本目录认定为官方发布者的签名身份签名。
内容摘要
sha256:b90b86532f3a2897b2765df1661752c013a341768fef319181831b439bbb64c3
发布时间
2026-11-10T10:09:43Z
签名身份
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:f032512dbae6bc24edbea94f0f18532fc943c293519a9afe688184fa185aeb44

此版本的引用

oci://hub.aggrega.ai/component/core/ai-pipeline/argo-workflows:1.0.0

开发者参数

开发者在 Aggregate 中设置的值。

名称类型默认值必需描述
install_crdsbooleantrue否Installs the Workflow custom resource definitions with the release. Turn it off when the definitions are managed out of band; the controller reconciles nothing until they exist in the cluster.
workflow_namespacesarraydefault否Namespaces this controller runs workflows in. The role and role binding a workflow pod needs are created in each one, so a Workflow submitted to a namespace outside this list is not reconciled.
metrics_enabledbooleanfalse否Serves the workflow controller's own metrics, in the Prometheus format, over plain HTTP on a ClusterIP Service of their own, and publishes their address as `metrics_endpoint`; while false that key is empty. The port checks no caller, so anything that reaches it can read them.

运维规格

运维人员按环境调整的基础设施规格。

名称类型默认值必需描述
portinteger (min 1, max 65535)2746否Port the API server's Service listens on. Most operators should omit this and let the Recipe assign the default (2746).
source_versionstring—否Source artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility.
computeobject—否—
overridesobject (open)—否Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

输出契约

此组件通过 uses 拓扑向使用方发布的值。

名称类型默认值必需描述
hoststring—是In-cluster DNS name of the Service fronting the workflow API server. A consumer that submits or queries a run dials this name together with `port`.
portinteger—是TCP port that Service accepts API requests on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default.
protocolstring—否How the published address is spoken to — `http`, so a consumer knows to submit runs over the HTTP API rather than a stream or an RPC channel.
metrics_endpointstring—否The full address Prometheus scrapes the workflow controller's metrics at — scheme, host, port and path, `http://<host>:8080/metrics`, the host being the controller's own metrics Service rather than the API server's. Empty while values.metrics_enabled is false.

uses 套接字

此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。

未声明 uses 套接字。

附加槽位

Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。

未声明附加槽位。

自注入允许列表

未声明自注入管道。

关系

与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。

使用

此实体未使用目录中的任何内容。

被使用

Component 概念参考 →

Aggrega 目录 — 收录组件、功能、配方以及渲染它们的插件的开放索引。

基于共享的 Aggrega 设计系统构建。

隐私