|
- Argo (events) Trigger an existing . . . - Stack Overflow
I'm trying to trigger a pre existing ClusterWorkflowTemplate from a post request in argo argo-events I've been following the example here, but i don't want to define the workflow in the sensor- I
- Argo-workflows install and run in specific namespace
I am trying to solve a scenario where argo-cd is installed cluster-wide, and we have to install the argo-workflows application within a separate namespace Let's say team-1 has a namespace team-one
- Getting a value from a ConfigMap in my Argo Workflow
Run argo submit with your new workflow file That's it :) I made the smallest template I can that should produce the exact same result If you run Argo locally like I do, maybe give it a try: apiVersion: argoproj io v1alpha1 kind: Workflow metadata: generateName: test- spec: entrypoint: main arguments: parameters: - name: cluster value: "stg
- How do I view the logs from a task in Argo? - Stack Overflow
The default container names on an Argo Workflows pod are init, main, and wait I'm not sure what message-passing-1-t8749 refers to, but it might be the "step task name "
- argoproj - Trigger Argo Workflow with webhook - Stack Overflow
I have a use case where I want to trigger a argo workflow when github push events occur So far from what I understand the following would be the steps of my approach, Create Github webhook and then
- Triggering steps in argo workflow using argo events
You can break down you steps into different argo workflows Then leverage argo events to tie up those workflows together For eg: There are quite few ways to configure your event source with argo events You can configure gcp pubsub or kafka topic as your event source for each workflow
- argoproj - Not able to load argo workflow UI - Stack Overflow
Not able to load argo workflow UI Asked 3 years, 1 month ago Modified 3 years ago Viewed 3k times
- How can I use Argo Workflows templates in Helm?
It is possible I've been on a team that regularly deployed Helm-templated WorkflowTemplates There are two ways to work around the Helm Argo template tag collision (As you know, the issue is that Helm's Go templating language and Argo's templating language both use {{}} to denote templated areas ) Option 1: The first way is to carefully nest the tags For example, if I want to use {{steps
|
|
|