[HN Gopher] Show HN: Atlas - A deployment pipeline platform buil...
___________________________________________________________________
Show HN: Atlas - A deployment pipeline platform built on Argo CD
Atlas is an open-source deployment pipeline platform built for
cloud-native applications. Atlas allows users to: - Create
continuous pipelines across all their environments and clusters -
Add custom tasks/tests plugins (Python scripts, K8S manifests, Argo
Workflows, environment setup, etc.) - Automatically rollback
applications in case of failure or degradation (Atlas watches the
application past the scope of a pipeline run to ensure and enforce
stability) - Use all existing Argo features Would love to hear all
of your feedback and thoughts on this!
Author : mihirpandya
Score : 36 points
Date : 2022-02-01 16:09 UTC (6 hours ago)
(HTM) web link (greenops.io)
(TXT) w3m dump (greenops.io)
| ellisv wrote:
| I'm a big fan of Argo CD (and their other products), so am
| interested to learn more about Atlas.
|
| > To build deployment pipelines with Argo Workflows, users have
| to set up Argo Events and write custom scripts to trigger an
| ArgoCD deployment, which can be a complicated process.
|
| It sounds to me like the major value-add, compared to Argo
| Workflows, is simplifying the implementation process - but then
| the first step in "Getting Started" is to setup Kafka...
|
| I'll have to spend more time looking at this.
| mihirpandya wrote:
| 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).
| johnmarcus wrote:
| can't workflows do these things?
| mihirpandya wrote:
| 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.
___________________________________________________________________
(page generated 2022-02-01 23:02 UTC)