|
- kubernetes - Argo Workflow: Permission issue with `system . . .
The service account is attempting to patch pods in the default namespace, but it only has patch permissions for the argo namespace To fix this, run the workflow in the argo namespace or add a new Role and RoleBinding to the default service account
- Argo Workflows template - Stack Overflow
Argo Workflows template - how to create conditional parameter based on runtime information Asked 2 years ago Modified 1 year, 11 months ago Viewed 4k times
- Cannot run Argo Workflow from the UI - Stack Overflow
The answer to your question on how to make argo workflow publicly? Is answered in Phase 2 Phase 1 - Local development mode Step (1): Disable client AuthN The argo-server (and thus the UI) defaults to client authentication so let's first disable it You can add the following setup in the Helm chart values: server extraArgs: [--auth-mode=server]
- 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
- 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
- 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
- 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
If I use item data bucket_url or item data['bucket_url'], it doesn't work and I get errors from Argo I tried to manipulate the output using sprig but I wasn't able to find a solution Basically I'm trying to fetch bucket_url to use in another template within this workflow Reproduce the issue yourself Run your Argo server Create a Workflow
|
|
|