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.

Pulumi Community

No necessarily, it’ll wait until the manifest resource returns an output. If you want to properly await the install of the service, use some logic inside an apply or convert the manifest to Pulumi code. I have an Argo cd example in python I can send in a few mins

Thanks. Yeah, I had originally wanted to stick with their upstream raw manifest for simplicity, but if converting it to pulumi is the easiest way then that’s fine by me, it’s not a particularly complex install other than perhaps the CRDs which should only need to be installed so should be handleable.

<https://github.com/jaxxstorm/pulumi-examples/blob/main/python/aws/eks_helm_argo/__main__.py>

I generally only use the `ConfigFile` resource for install CRDs, everything else you can pipe through `kube2pulumi`

It looks like this uses helm. I have weirdly managed to avoid learning anything about helm so far, not out of any opinion on helm of mine but just from circumstance. Is there anything I should know about needing it here? Is there any magic it’s adding beyond the creation of the necessary argocd resources in k8s?

nope, you can replace the helm part by just dojng `kube2pulumi` on that install manifest

Hrm, it looks like `kube2pulumi` has a bug related to lists of objects with only one key:

```❯ kube2pulumi python -f not-crds.yaml
Error: Error: Missing item separator

  on pcl-1017078102.pp line 1301:
1298: ports = [
1299: {
1300: containerPort = 5556
1301: }
1302: {

Expected a comma to mark the beginning of the next item.```
The relevant section seems to be:

```        ports:
        - containerPort: 5556
        - containerPort: 5557
        - containerPort: 5558```
If I change this to:

```        ports:
        - containerPort: 5556
          name: foo
        - containerPort: 5557
          name: bar
        - containerPort: 5558
          name: baz```
then processing proceeds to the next section where this construct exists.

Hmm, I can’t tell, is it an extension of this? <https://github.com/pulumi/kube2pulumi/issues/65>

Added a comment there. Thanks again for the help :slightly_smiling_face: I’m going to move on and just leave this as a documented TODO… at the end of the day, exporting the LB’s IP is just a convenience for development and in practice all dev environments are going to just use `minikube tunnel` and localhost