2021年Argo Workflows调查持续了三周。共有60份回复。最终的NPS得分高达66分。
也许不出所料,大多数是工程师:
这与我们基于所知道的主要用例所期望的紧密相关。
六个用例占主导地位:
由于受访者倾向于DevOps工程师,这可能夸大了基础设施自动化和CI/CD用例的比例。
我们很高兴看到模板和API如此流行:
有趣的是,我认为我们期望更多的人使用一种不同的语言客户端。semaphore和mutex都比我们预期的要低,但这些都是非常新的特性。
YAML是主要的挑战;许多用户更熟悉Python(提到7次)。
熟悉云原生和容器也是一个挑战(提到了3次)。
“Convincing folks that containers aren’t scary and YAML isn’t evil”
提供一个Python DSL(5次提及)。值得注意的是,用于Argo Workflows的Python DSL已经以Couler[1]的形式存在了(了解如何使用Python编写工作流[2])。
“Honestly, something like a good python DSL would be fantastic”
改进(提到3次)。Argo workflow v3.0有一个改进的用户界面[3]。
文档也被提到作为一个需要改进的领域(3次)。
“I do find that often features we want exist already but can be a little difficult to discover” “I think the docs sometimes feel a little bare or like they don’t have enough structure.” “Improve UI, multi-cluster, docs”
用户喜欢它是云原生/Kubernetes(提到28次)
最佳工作流管理器(大约提到6次)
“Best workflow manager on K8S” “the best K8s orchestrator we found” “one of the best cloud native tools i’ve ever seen” “better than other frameworks that were evaluated” “Best workflow manager on K8s.” “Because its the best to manage DAGs in the industry”
相对轻量级和易于使用(提及5次)
“…lightweight, kubernetes native. Great community.” “we wanted more flexibility...” “Its way faster…” “so much more powerful…”
与Argo CD配合良好(提到5次)
“We picked it for the easy integration with ArgoCD” “We were already using ArgoCD. The doc/community/concepts felt good. We managed to get satisfying state quickly.”
目前我们考虑:
[1]
Couler: https://github.com/couler-proj/couler
[2]
了解如何使用Python编写工作流: https://blog.argoproj.io/authoring-and-submitting-argo-workflows-using-python-aff9a070d95f
[3]
Argo workflow v3.0有一个改进的用户界面: https://blog.argoproj.io/argo-workflows-v3-0-4d0b69f15a6e