This message was deleted.

sparse-intern-71089

06/02/2023, 10:35 AM

This message was deleted.

better-dentist-3207

06/03/2023, 6:57 PM

For ArgoCD: kinda complicated but doable, I built something similar (for cdk8s, not pulumi) 1. Pulumi Kubernetes provider can output yamls to a directory instead of applying them directly, using the opt

renderYamlToDirectory

2. You can write a sidecar based ArgoCD Config Management Plugin (CMP). Sidecar image contains pulumi binaries and a config spec file that defines stuff like pulumi stack name that you want to interact with 3. With the plugin spec defined, you can explicitly use a plugin in an ArgoCD Application manifest and pass on parameters defined in the spec. 4. Now, in the ArgoCD Application manifest, instead of setting the path to a kustomization dir or a helm chart, you set the path to the entire pulumi project, and under

plugin:

you specify a Stack + Env, custom values whatever you need, using the spec you defined.

better-dentist-3207

06/03/2023, 6:59 PM

https://argo-cd.readthedocs.io/en/stable/operator-manual/config-management-plugins/

better-dentist-3207

06/03/2023, 6:59 PM

Here is the ArgoCD doc for CMPs

better-dentist-3207

06/03/2023, 7:04 PM

Important: make sure you use ArgoCD version >= 2.6.0. You weren't able to explictly define a plugin to use in an application before that, and had to implement the

.spec.discover

field in the CMP spec, which was just unfeasible for a project like pulumi and cdk

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.