Hey y'all, crossposting this thread from <#C01PF3E...
# kubernetes
Hey y'all, crossposting this thread from #getting-started here: https://pulumi-community.slack.com/archives/C01PF3E1B8V/p1650599095566589 Long story short: the example on https://www.pulumi.com/registry/packages/kubernetes/api-docs/apps/v1/statefulset/#create-a-statefulset-with-auto-naming results in the statefulset never being created because of a circular dependency. Pulumi starts by creating the service, but the statefulset's
, so the statefulset waits for the service to become ready. The service never becomes ready though, because it's waiting for pods matching it's selector to be created. These pods would be created by the statefulset, but Pulumi is not creating the statefulset until the service is ready
Any reason you can't just pull the name out into a local variable, like you've done with
? That would solve the problem of the constant being repeated. Hardcoding service names is generally fine. The only things I've had issues with giving fixed names to are Secrets & ConfigMaps.
Add an annotation to the service:
<http://pulumi.com/skipAwait:|pulumi.com/><http://pulumi.com/skipAwait:|skipA><http://pulumi.com/skipAwait:|wait:> false
A bug report was made by @billowy-army-68599 here: https://github.com/pulumi/pulumi-kubernetes/issues/1974 See the linked thread for more details