|
- 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
- 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
- ArgoCD - what need be done after build a new image
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!
- Unable to add repository to ArgoCD - Stack Overflow
We're currently trying to provision a High-Availability ArgoCD instance onto our Kubernetes cluster using the argocd helm chart (7 2 0) to provision our applications Our infrastructure is on AWS a
- 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
- Fixing out of sync warning in Argo CD - Stack Overflow
Argo CD shows two items from linkerd (installed by Helm) are being out of sync The warnings are caused by the optional preserveUnknownFields: false in the spec section: trafficsplits split smi-spe
- How to use Workload Identity when configuring external clusters in Argo CD?
I think Workload Identity is supported for adding external (AKS) clusters in Argo CD but I can't find a detailed guide anywhere for how to do this The official docs contain some info about how to configure kubelogin to achieve what I want, but this isn't a complete guide
|
|
|