mihirpandya

Hi! Sorry for the delayed response. Atlas focuses more on deployment pipelines, and is a more structured system for deployment-specific use cases. It has a lot of support for testing, application recovery, and state remediation.

Tekton is quite similar to Argo Workflows - they are both frameworks that provide ways to declare workflow pipelines for execution on Kubernetes. Per one of the Argo project leads, the majority of the users are using these workflows for ML, ETL, data processing pipelines, and CI.

Any suggestions for other names?

Argo Workflows would need to be fully configured with Argo Events and Argo CD to make this happen, specifically with additional Workflows for error processing, multiple sensors for input, and a secondary tier of custom sensors for watching tasks or Argo CD apps past the pipeline run. The workflows (main pipeline and handling pipelines) would likely require custom logic as well. Definitely feasible, but can be complicated.

Thanks for the comment. Fair point about Kafka :), although there are good tools now when it comes to deploying Kafka easily (Strimzi, Confluent, etc.).

I like to think of Atlas as connective meshing for Argo which adds a reactive element. Atlas can connect tasks/tests, deployments, and automated stability under one standardized interface. It also adds a lot of automation, picking up feedback/changes at any point during the lifecycle and making changes based on it (rollback, progression, etc).