jessesuen

4 ms·

1. 1.▲
   by jessesuen 7y ago

   Lead and core contributor to Argoproj here. I agree that Tekton and Argo Workflows share a closer comparison than with Argo CD (despite the "CD" acronym appearing in the name Tekton CD). Workflows is aimed to be a more general pur
2. 2.▲
   by jessesuen 8y ago

   Thanks. We've updated the docs to outline the bare minimum set of privileges.
3. 3.▲
   by jessesuen 8y ago

   Docs have been updated and linked to in the getting started guide: https://github.com/argoproj/argo/blob/master/docs/workflow-r...
4. 4.▲
   by jessesuen 8y ago

   Thank you. We didn't submit the post, but we actually have https://argoproj.io which redirects to the argoproj.github.io page. Actually we've been meaning to take advantage of GitHub's custom domain so we can drop
5. 5.▲
   by jessesuen 8y ago

   I always explain that Workflows should be thought of as a fancier version of Kubernetes Jobs. Some of the killer features, IMO, are with artifact management and control flow (e.g. loops, conditionals, parallelism). So far, our most common u
6. 6.▲
   by jessesuen 8y ago

   I work on Argo. Those instructions are mainly for demo purposes because many of the examples need admin privileges. The amount of access which is needed, is really dependent on what your workflow is doing (e.g. if your workflow needs to dep
7. 7.▲
   by jessesuen 8y ago

   I work on argo. The workflow-controller is very tolerant to crashes and designed to be this way. Workflow state is captured in the workflow CRD object (in k8s etcd). Because step names are formulated, in the event of a crash (say before the