|
- 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
- What is the default password of argocd? - Stack Overflow
user: admin To get the password, type the command below: kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{ data password}" | base64 -d
- 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
- 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
- ArgoCD Ingress Kubernetes Too Many Redirects even With --insecure . . .
A common solution when installing ArgoCD to solve that properly is adding the --insecure flag to true for the configmap yaml to populate the environment variables used by argo-server: apiVersion: v1 kind: ConfigMap metadata: labels: app kubernetes io name: argocd-cmd-params-cm app kubernetes io part-of: argocd name: argocd-cmd-params-cm data: server insecure: "true" # <-- this line need to be
- 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
- 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
|
|
|