This message was deleted.
# getting-started
s
This message was deleted.
g
Interesting you say baking the manifests to YAML for ArgoCD is cumbersome since GitOps is the direction we are slowly taking. There are some pros and cons. I do know Pulumi lets you just render the YAML for this purpose. It's a workflow that we may end up going with since we started using ArgoCD with helmfile (currently). However, I've used the Pulumi k8s provider before and it works great as a way to abstract away the gotemplate and do last-mile transforms.
d
I’d like to discuss this too - we have ephemeral aks environments, with a “project” stack to set up the main RG/Storage/Loganalytics and then developers start up as many stacks (aks clusters) as they want - which make use of the aforementioned bits. Devs are simply working with az cli + pulumi directly. We don’t yet have the per-dev environments checked into source control + pipelined.
c
@damp-honey-93158 have you considered using something like https://loft.sh? It's great for dev/ephemeral environments.
As for my problem; I intend to try to solve it with the new Deployments API, Unleash, Keptn & Flagger for progressive continuous delivery/deployment.
d
@curved-application-45650 I haven't looked at this - mostly because I was trying to build a pulumi/stack based system that replicates production for use in dev - and secondly because I didn't know it existed 🙂 Thanks for the tip though!