#Correct. You have to share the volumes

1 messages ยท Page 1 of 1 (latest)

daring pulsar
#

@meager tulip - Thanks for the replies.
My last question is, how do I get the env entry into the helm install?

meager tulip
#

Are you referring to the helm install of the engine?

daring pulsar
#

Yes.

meager tulip
#

So what I shared above is actually for the pods that will connect to the dagger engine. Not for the dagger engine itself!

#

That env variable is what the dagger CLI uses to connect to the engine. So wherever you'll run the CLI, that is where the env variable needs to be

daring pulsar
#

Ahhhh... Ok. Got it. Oh duh.... ๐Ÿคฆ๐Ÿปโ€โ™‚๏ธ

#

Hmm... (thinking out loud)...I'm going to need to create a new template for this connectivity for my CI development. (I'm using Coder for remote dev environments.)

Cool!!! I'm almost there.

Thanks again!

meager tulip
#

No problem! I'm currently working on a new setup of Dagger engines + github runners to run our workloads. The idea is to have a setup that is fully dynamic. Basically developrs can write: runs-on: dagger-<VERSION> (e.g runs-on: dagger-v0-10-1) or any other version they like, and everything will get automatically spawn up and connected for that particular dagger version.

I'm happy to do a live demo if that is useful for you! I will be writing a blog post about this setup and I expect to have it published the week of the 25th of March

cc @dry relic

daring pulsar
#

The idea is to have a setup that is fully dynamic.
That's my goal too, but via webhooks and Argo Workflows and not have devs mess with anything. ๐Ÿ˜› Basically, CI workflow will be "kicked-off", when a commit is made and CD will be kicked off when a PR is made. What is done in each workflow will be very opinionated. ๐Ÿ™‚

warm lava
meager tulip
#

Hey Nadir! Its on the works, almost ready to be published so its coming very soon! Definitely by next week ๐Ÿ’ช

crystal eagle
#

please let us know once it's live!

meager tulip