|
- ArgoCD always redirects to HTTPS - Stack Overflow
global: server: insecure: true We can kubectl get configmap argocd-cmd-params-cm -n {argo-cd namespace} -o yaml to verify the configurations to be applied to the server
- kubernetes - Can ArgoCD deploy a Helm chart from Git repository, not . . .
Helm chart gets successfully deployed when run outside of ArgoCD with helm install guestbook --namespace guestbook from the root of the cloned git repository with the chart Git repository and access credentials are configured in ArgoCD dashboard and ArgoCD connects to the repo successfully
- cicd - ArgoCD GitOps declarative config: How to store repo creds in a . . .
How can we bootstrap all the needed repositories without doing so? I am aware of at least one workaround: I could use the argocd CLI app in our K8s cluster to populate the repo-creds (or even plain kubectl apply for that matter) But then, what is the point of ArgoCD to programmatically support repo-creds credentials via gitops?
- kubernetes - How to login to ArgoCD CLI non-interactive in CI like . . .
We have a full-blown setup using AWS EKS with Tekton installed and want to use ArgoCD for application deployment As the docs state we installed ArgoCD on EKS in GitHub Actions with: - name: Inst
- ArgoCD - what need be done after build a new image
Now, developers will update the codes, after commit changes, a gitlab pipeline automatically runs and build a new image and override to tag latest with other tags and push to private docker registry So what's the next step in ArgoCD? How argocd know the application is changed, and need be redeployed, and the image:latest need be pull again?
- Triggering ArgoCD webhook using Github Actions
If above workflow was run manually using workflow_dispatch event, then github event has different payload than the ArgoCD Webhook expecting You can check argocd server logs for more info about this webhook event
- kubernetes - Argo CD argocd-autopilot error ComparisonError rpc error . . .
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
- What is the default password of argocd? - Stack Overflow
kubectl -n argocd scale deployment argocd-server --replicas=1 New password of the ArgoCD will be your api-server pod name with the numbers at the end name (kubectl -n argocd get pods >> to find pod name) i e login: user: admin pass: argocd-server-6cdb9b4b84-jvl58 That should work
|
|
|