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.
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...
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
Argo can't do this. And I think annotating applications for this is seriously stupid (why? I just wanna updated to the latest tag!). So the working way is to periodically get the Application kind in the argocd namesapce, get the repo and then check for updates. If there is an update, then roll out restart the deployment!
In Argo Workflows, each step runs in its own container, so files created in one step (container) are not automatically available in another step. To share files (like your docker.file) between steps, you need to use a shared volume (such as an emptyDir or a PersistentVolumeClaim).
1 i have responded to your issue in argocd-autopilot issues page. i think you might be running an outdated version to the binary. the original problem was with the argo-cd.yaml file tries to reference bootstrap\argo-cd, while it should be bootstrap/argo-cd - this issue was resolved in v0.4.11
Multiple sources for a helm chart: I have configured multiple sources to fetch helm templates from one repo and values from different repo. apiVersion: argoproj.io/v1alpha1 kind: Application metada...
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."
Argo becomes completely non-functional if this service is not present. Additionally, since Argo can't determine what's missing, it cannot re-create the service itself. You will have to recreate the service manually, which may mean helm template 'ing or running kustomize build . to render the manifest for the service and re-applying it.
How to pass list of arguments from argo workflow and use it in argo workflowtemplate Asked 3 years, 7 months ago Modified 3 years, 7 months ago Viewed 8k times
