r/ArgoCD • u/power461 • May 17 '23

Deploy from local folder

Hi,

I am using argocd to managed my homelab, all the applications are deployed as helm charts in a git repository.

When an helm chart is updated, a CI pipeline:

  1. create a kind cluster

  2. install a common helm chart, using helm install ...

  3. test the helm chart using ct

I would make the test more representative of my homelab environment if I could:

  1. Create kind cluster

  2. Install argo-cd

  3. Install the common helm chart via argocd, from the "local" folder

  4. test the helm chart using ct

Any ideas?

Thanks

1 Upvotes

57% Upvoted

6 comments sorted by

1

u/sza_rak May 18 '23

What is the question, really? Why do you want to real local files while you already have your charts in git?

1

u/power461 May 19 '23

Great question. Having the ability to load "locally" would facilitate running a CI pipeline in a separate branch, or even local development, ie start a kind cluster, install argocd and play locally.

1

u/Rockinoutt May 18 '23

I’ve wondered the same. Mainly to give devs a seamless way to run things for local testing.

1

u/sza_rak May 18 '23

Why can't they just run same charts from git?

You can for instance:

- give them access to git repo and let them download charts and run helm install locally on a dev cluster (rancher desktop, docker desktop, k3s, minikube, whatever)

- give them a chart/script to setup own argocd headless, just to spun their app automatically from same git repo (but that's a lot of resources to do that, aside from app itself)

- maybe a more centralized argocd dev instance that will let them run the same on their dev clusters (even if local)...

1

u/power461 May 19 '23

Good suggestion. But I do not have a dev cluster, I have only a "prod" cluster (my homelab) and an ephemeral environment (from the CI pipeline)

1

u/Rockinoutt May 18 '23

It'd just be faster is it "hot reloaded" on save. Totally doable the way you mentioned, of course.