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.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:b90b86532f3a2897b2765df1661752c013a341768fef319181831b439bbb64c3
Published
2026-11-10T10:09:43Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/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

Reference at this version

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

Developer parameters

Values the developer sets in the Aggregate.

NameTypeDefaultRequiredDescription
install_crdsbooleantruenoInstalls 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_namespacesarraydefaultnoNamespaces 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_enabledbooleanfalsenoServes 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.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
portinteger (min 1, max 65535)2746noPort the API server's Service listens on. Most operators should omit this and let the Recipe assign the default (2746).
source_versionstring—noSource artifact version (Helm chart). Overrides the Recipe's default source version. Changing from default does not guarantee value mapping compatibility.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-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—yesTCP 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—noHow 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—noThe 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 sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

No uses sockets declared.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

No self-inject pipes declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

This entity uses nothing in the catalog.

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy