copy and paste this google map to your website or blog!
Press copy button and paste into your blog or website.
(Please switch to 'HTML' mode when posting into your blog. Examples: WordPress Example, Blogger Example)
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
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
How to hide secret values in Inputs and Outputs parameters shown on UI . . . I personally would not expose Argo Workflows as the UI for an end user I'd use that as the runtime to execute the jobs, but have a UI in-front that takes the inputs on behalf of the user, and in the background calls Argo Workflows with the details This will also give you more flexibility on the UI side
Argo workflow stuck in pending due to liveness probe fail? entrypoint: channels My argo workflow ends up getting stuck in the pending state I say this because I check my orderer and peer logs but I see no movement in their logs I referenced Argo sample workflows stuck in the pending state and I start with getting the argo logs: [user@vmmock3 fabric-kube]$ kubectl logs -n argo -l app=workflow