Concepts
Definitions of Pipekit's core terms.
Pipekit introduces a handful of terms on top of Argo Workflows. This section defines each one and points into the task-oriented documentation under Using Pipekit for the day-to-day surface.
If you're new to Pipekit, start with Workflow vs Pipe vs Run. It disambiguates the three terms readers most often confuse.
Core terms
Pipe: A logical container for one Argo
Workflowdefinition and the history of every run of it.Run: A single execution of a Pipe.
Workflow vs Pipe vs Run: Disambiguating Argo's
Workflow, Pipekit'sPipe, and Pipekit'sRun.Cluster: A Kubernetes cluster registered with Pipekit.
Organization: Pipekit's top-level tenant.
Pipekit Agent: The in-cluster component that brokers commands and status between Pipekit and Argo.
Templates: Reusable
WorkflowTemplateandClusterWorkflowTemplatedefinitions Pipekit manages across clusters.Cron & Externally Triggered: Execution models that bypass direct submission.
Access Control: Workspaces, roles, and IdP group bindings.
Pipekit Cloud vs Self-Hosted: Deployment models, side by side.
Last updated