使用 Homebrew, scoop 安装 argo

项目链接

• 主页
• 仓库

命令和别名

• argo

项目历史

The argo-workflows GitHub repository was created in August 2017. Over time it became one of the four main Argo subprojects alongside Argo CD, Argo Events, and Argo Rollouts. Its README describes the broader Argo project as a collection of tools for getting work done with Kubernetes and identifies Argo Workflows as the container-native workflow engine.

The project matured from a Kubernetes workflow controller into a CNCF graduated project with documented governance, maintainers, community meetings, release branches, client libraries, and security process. Official releases now span both the 3.x maintenance line and the 4.x line, with Homebrew packaging the `argo` binary from argoproj/argo-workflows tags.

采用历史

Argo Workflows' own README calls it the most popular workflow execution engine for Kubernetes and says about 200+ organizations officially use it. The official USERS.md list includes large technology, finance, cloud, media, and AI/data companies, and the Argo repository points each subproject to its adopter list. Its use cases page and README emphasize machine-learning pipelines, data and batch processing, infrastructure automation, CI/CD, and other Kubernetes jobs.

The ecosystem around it is broad: the README names Argo Events, Hera, Katib, Kedro, Kubeflow Pipelines, Netflix Metaflow, Seldon, SQLFlow, and others as projects that use or rely on Argo Workflows. That adoption pattern made the CLI useful not only for direct workflow authors, but also for platform teams building higher-level ML, data, and batch-compute systems on Kubernetes.

使用方式

Users define Workflows or CronWorkflows as Kubernetes YAML and use the `argo` CLI to lint, submit, list, watch, retry, resubmit, suspend, resume, terminate, and inspect them. The workflow controller then schedules each step as a container, supports artifacts and parameters, handles DAG or step sequencing, and integrates with Kubernetes-native scheduling, service accounts, volumes, and secrets.

The Homebrew formula builds the CLI from source and tests `argo version` plus `argo lint --kubeconfig`, reflecting the package-manager view of Argo as a local Kubernetes client tool. In actual clusters, the CLI is paired with the controller, CRDs, optional UI/server, archives, metrics, and SSO features documented by the project.

为什么软件包爱好者会关心

Argo Workflows is significant because it turned Kubernetes CRDs into a mainstream packaging and operations surface for workflow engines. A package install gives you a local `argo` binary, but the real artifact is a contract with cluster-side CRDs, controllers, Helm charts, and YAML manifests, making it a canonical example of cloud-native CLI packaging.

For package maintainers, it also illustrates a common modern split: the Homebrew formula builds one CLI executable, while the upstream project simultaneously publishes controller images, manifests, docs, examples, SDKs, and a larger CNCF-governed ecosystem.

时间线

• 2017: argo-workflows GitHub repository created.
• 2020: Argo Workflows user survey summary published by the Argo project.
• 2021: Argo Workflows user survey results published by the Argo project.
• 2022: v3.3.6 is the earliest GitHub release visible through the releases API snapshot used for this enrichment.
• 2023: Argo Workflows and Events user survey results published.
• 2026: v4.0.x and v3.7.x release lines are both active in GitHub releases.

Related projects

• The official Argo project groups Argo Workflows with Argo CD, Argo Events, and Argo Rollouts. The README also points to client libraries including Go, Java, Hera for Python, and Juno for TypeScript.

来源

• https://api.github.com/repos/argoproj/argo-workflows
• https://api.github.com/repos/argoproj/argo-workflows/releases
• https://github.com/argoproj/argo-workflows#readme
• https://github.com/argoproj/argo-workflows/blob/main/USERS.md
• https://github.com/argoproj/argoproj#readme
• https://raw.githubusercontent.com/Homebrew/homebrew-core/HEAD/Formula/a/argo.rb