So I’m looking at using garden to build a consistent development environment with my companies production / staging environments. We’ve gravitated to garden due to it’s support with Helm and it’s helm like structure. I’ve been working on getting a simple PoC setup but am running into a number of problems just getting garden to work reliably. I’m using the recommend setup (Docker for Mac) with Kubernetes enabled (ofc).
When I run the command
garden deploy after initializing a project. It runs perfectly the first time outputting.
✔ providers → Preparing environment... → Done ✔ local-kubernetes → Configuring... → Ready ✔ providers → Getting status... → Cached ℹ Run with --force-refresh to force a refresh of provider statuses. ✔ providers → Getting status... → Cached ℹ Run with --force-refresh to force a refresh of provider statuses. ✔ default-backend → Getting build status for v-63466f0842... → Done (took 0 sec) ✔ default-backend → Deploying version v-63466f0842... → Done (took 8.4 sec) ℹ default-backend → Resources ready ✔ ingress-controller → Building version v-82d30a9ab9... → Done (took 5 sec) ✔ ingress-controller → Deploying version v-82d30a9ab9... → Done (took 28.6 sec) ℹ ingress-controller → Resources ready
After this first launch subsequent “deploy” calls cause the “providers → getting status” section to completely hang. If I cancel the command that is doing absolutely nothing I notice that a left over process consuming around 100% cpu of a single core is left hanging around. I’ve tried leaving it alone for 20 - 30 minutes and it does absolutely nothing but just consume resources etc.
I can still access my kubectl environment but garden is just dying very silently doing nothing. I’m not really sure what else to include would appreciate it if someone could give me some advice.