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-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
How to trigger argo workflow from an API request? Use Argo Events Argo Events is a separate but closely-related project It can accept a variety of inputs (webhooks, pub sub messages, etc) and then trigger a Workflow Argo Events could make sense if, for example, you want an external record of all the workflows submitted Pub sub would give you that record Use the Kubernetes API or CLI
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
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 workflow stuck in pending due to liveness probe fail? 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:
Argocd application resource stuck at deletion - Stack Overflow If your problem is that the namespace cannot be deleted, the following two solutions may help you: Check what resources are stuck in the deletion process, delete these resources, and then delete ns Edit the namespace of argocd, check if there is a finalizer field in the spec, delete that field and the content of the field Hopefully it helped you
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