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

Stuck on a small chicken and egg problem. I have a k8s deployment which needs the ip of the loadbalancer service, and the service matches the deployment. so they both depend on each other. When use the annotation to skip await the service, the deployment  fails because the ip is not there yet. Any idea how to get around this?

I asked this before i just saw while searching, ony now the workaround is not possible as this service needs the IP address <https://pulumi-community.slack.com/archives/C84L4E3N1/p1625820295022000>

The fact that the Deployment depends on the Service and vice versa seems like a bad ordering problem, one you'd be challenged with regardless, no?

I need to set the external IP address to configure p2p announce addresses. Typical guides have you spin everything up and then reconfigure manually, but that is not whati want to do :wink: