Credential-Zugriff
Reads kubeconfig, Argo tokens, workflow parameters, and secret references.
brew
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für argo in AI-Agent-Workflows.
Agent-Sicherheit
argo controls Argo workflows and cluster-executed jobs.
Reads kubeconfig, Argo tokens, workflow parameters, and secret references.
Can submit, stop, delete, and retry workflows in clusters.
Can trigger jobs that build, deploy, or process artifacts.
Gate submit, delete, retry, and token-backed workflow commands.
Allow workflow status reads; require approval for submissions and destructive operations.
Installation
brew install argolocal Homebrew formula metadata
scoop install main/argoScoop official bucket manifest trees · bucket/argo.json · Quelle: api.github.com
Überblick
Get stuff done with container-native workflows for Kubernetes
Verlauf
Argo Workflows is the Argo project's Kubernetes-native workflow engine. The project implements workflows as Kubernetes custom resources, models work as container steps or DAG tasks, and ships the `argo` CLI for submitting, linting, watching, and managing workflow objects.
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.
Sicherheitslage
infrastructure mutation or orchestration signal.
orange Risiko · mittel Konfidenz · infrastructure
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
argo | cli | globales Executable |
Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
https://github.com/argoproj/argo-workflows
Installationsmetadaten
| Paketschlüssel | brew:argo |
|---|---|
| Version | 4.0.8 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/argo |
| Homepage | https://argoproj.io |
| Repository | https://github.com/argoproj/argo-workflows |
| Upstream-Dokumentation | https://argo-workflows.readthedocs.io/ |
| Lizenz | Apache-2.0 |
| Quellarchiv | https://github.com/argoproj/argo-workflows.git |
| Zuletzt aktualisiert | 2026-07-22T12:03:14Z |
| Pulse | updated |
| Build-Abhängigkeiten | go, node, yarn |
| Bottle | verfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | argo |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
Source-Datenbank-Treffer
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
main/argo
scoop install main/argoQuellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.