Very very small suggestion: its not very expensive to register a domain and have it redirect to the github pages; might make it appear somewhat more polished.
Argo: Open source Kubernetes native workflows, events, CI and CD
11–20 of 21 posts
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#12What does this project simplify? It seems to be equivalently complex to the process it would have you replace.
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 use case has been in the machine learning space. One of the biggest problems it can solve is the ability to leverage a Kubernetes cluster as an auto-scaling compute grid for all forms batch processing. We've been working closely with ML teams at various companies, both large and small, and many of our features were implemented to address the ML use cases (e.g. DAG support, loops/step expansion, step aggregation).
With that said, Argo got its start trying to address the CI use case, so we also feel like we handle that one pretty well.
The workflow controller has always been intended to be a lego block to enable higher level applications to be built on top of it.
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#13Very very small suggestion: its not very expensive to register a domain and have it redirect to the github pages; might make it appear somewhat more polished.
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 the github.io entirely.
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#14The idea is nice, but if security is one of your concerns, you'll probably not want to run this if the docs are even close to representative of the actual application: > 3. Configure the service account to run workflows > For clusters with RBAC enabled, the 'default' service account is too limited to support features like artifacts, outputs, access to secrets, etc... Run the following command to grant admin privilege…
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 deploy a resource, then you need to give the service account 'create' privileges on that resource). Currently, the bare minimum for a workflow to function is outlined here: https://gi…
Docs have been updated and linked to in the getting started guide:
https://github.com/argoproj/argo/blob/master/docs/workflow-r...
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#15Earlier quoted context omitted.
While I agree with your position that admin rights should not be the default, that doesn't seem to be what Argo is actually doing. The text snippet you've included is from the quick start/demo page, which seems to be targeted at getting the examples running quickly so that a potential user can see what it is capable of. Other issues for this in a production setup would be the use of the 'default' role/namespace at al…
The parent post did quality it appropriately with "if the docs are even close to representative of the actual application". I hope the docs are not representative, but the parent post is right that it's a bad sign. At least put up a warning sign that it's insecure and only suitable for demo purposes to do that.
Thanks. We've updated the docs to outline the bare minimum set of privileges.
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#16Is there easy way to build containers ?
I see many resources for running stuff with already built container but could not any simple how to do it. Currently just mounting docker host and building on it.
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#17Very very small suggestion: its not very expensive to register a domain and have it redirect to the github pages; might make it appear somewhat more polished.
"that's like yout opinion, man"
registering vanity domains is a shure way to make this information harder to find in a few years
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#18Is there easy way to build containers ? I see many resources for running stuff with already built container but could not any simple how to do it. Currently just mounting docker host and building on it.
Dockerfiles?
Re: Argo: Open source Kubernetes native workflows, events, CI and CD
#19Is there easy way to build containers ? I see many resources for running stuff with already built container but could not any simple how to do it. Currently just mounting docker host and building on it.
Instead of using docker host you might run docker daemon in sidecar container.
Here is a sample argo workflow which uses this technique:
https://github.com/argoproj/argo/blob/master/examples/sideca...