cncf
/
toc
mirror of https://github.com/cncf/toc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
toc/projects/argo/argo-graduation-proposal.md

8.3 KiB
Raw Permalink Blame History

Argo Graduation Proposal

Since joining the CNCF in April 2020 as an incubation-level project, the Argo Project has made great progress in growing the community of contributors and users including the addition of Red Hat and Codefresh along-side BlackRock as partners in governing and running the project. On behalf of the Argo Project team, we believe that Argo is ready for graduation.

Description

The Argo Project is a set of Kubernetes-native tools for deploying and running jobs and applications on Kubernetes. All the Argo tools are implemented as controllers and custom resources. These tools can be used independently but are even more powerful when used together. As a CNCF graduated project, all top level projects must meet graduation maturity requirements.

Argo Workflows enables creation of complex parallel workflows as Kubernetes resources and is used in many different use cases from CI/CD pipelines to DAG-based ML training workflows. It is the workflow engine behind the open source Kubeflow Pipelines.

Argo Events provides declarative management of event-based dependencies and triggers for Kubernetes resources based on various event sources. A common use of Argo Events is to trigger Argo Workflows and to generate events for long-lived services deployed using Argo CD.

Argo CD supports declarative GitOps-based deployment of any Kubernetes resource, including Argo Events, services and deployments across multiple k8s clusters.

Argo Rollouts provides declarative progressive delivery of application resources using deployment strategies such as blue/green and canary for Kubernetes.

Each of these tools is built to be Kubernetes native and are implemented as controllers and Custom Resources. These tools can be used independently, but there is great benefit in using them together to create complex applications. Argo Events, for example, can kick off Argo Workflows which can generate and queue additional Argo Events which are processed by long-lived services deployed using Argo CD that use Argo Rollouts to control the deployment process.

Argo has been presented at Kubernetes community meetings, KubeCon conferences, and many other venues by both project members and the community at large.

Statement on alignment with CNCF mission

The Argo project is well-aligned with the CNCF’s mission to make cloud native computing ubiquitous. We are completely aligned to "empower organizations to build and run scalable applications" including the adoption of Kubernetes and declarative APIs. All the Argo tools are implemented as controllers and custom resources. They use/integrate with other CNCF projects like gRPC, Prometheus, NATS, Helm..

Sponsors / Advisors from TOC

  • Lei Zhang
  • Cathy Zhang

Project name

  • Argo

Unique identifier

  • argo, argoproj

Preferred maturity level

  • graduated

The Argo Community is looking for the following by becoming a CNCF graduated project:

  • Promote public visibility to add value to the CNCF mission.
  • Foster collaborative development to further the overall CNCF mission.
  • Closer integration and collaboration with other CNCF projects.
  • Reassurance for the Argo Community that the project will be a permanent part of the CNCF ecosystem well into the future.

License

  • Apache License 2.0

Source control repositories

External Dependencies

Argo depends on the following external software components:

  • Kubernetes (Apache Software License 2.0)
  • Dex (Apache Software License 2.0)
  • Redis (BSD)
  • React (MIT)
  • GRPC (Apache Software License 2.0)
  • Golang (Apache Software License 2.0)

Initial Committers

  • Alex Collins (Intuit)
  • Alexander Matyushentsev (Akuity)
  • Jann Fischer (Red Hat)
  • Jesse Suen (Akuity)
  • Jonathan West (Red Hat)
  • Oleg Sucharevich (Elastic)
  • Vaibhav Page (BlackRock)

Infrastructure requests

  • None

Communication Channels

Issue tracker

Website

Release methodology and mechanics

  • Major feature release about four times per year with additional minor/patch releases
  • Some users also run HEAD of master particularly for trying and testing release candidates.

Social media accounts

Existing sponsorship

  • CNCF, Intuit, Akuity, BlackRock, Codefresh and Red Hat are the sponsors of Argo

Community size

Argoproj

  • 25,000 stars
  • 14,000 slack members
  • 6,100 forks
  • 815 contributors
  • 240 end user companies and organizations

Production usage

Argo is known to be actively used in production by the following organizations:

Graduation State Criteria

Have committers from at least two organizations

The Argo governance committee consists of members from Intuit, Red Hat, Blackrock, and Codefresh. Committers are represented from a much broader set of organizations.

Have achieved and maintained a Core Infrastructure Initiative Best Practices Badge

Core Infrastructure Initiative Best Practices Badges have been completed and are being maintained.

Have completed an independent and third party security audit with results published of similar scope and quality as this example which includes all critical vulnerabilities and all critical vulnerabilities need to be addressed before graduation

Third party security audit has been completed with Trail of Bits and ADA Logics as the 3rd party auditors. https://github.com/argoproj/argoproj/blob/master/docs/argo_threat_model.pdf https://github.com/argoproj/argoproj/blob/master/docs/argo_security_final_report.pdf https://github.com/argoproj/argoproj/blob/master/docs/audit_fuzzer_adalogics_2022.pdf https://github.com/argoproj/argoproj/blob/master/docs/argo_security_audit_2022.pdf

Explicitly define a project governance and committer process

Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website)