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

This looked to be related, but it’s not clear how it would apply here: <https://github.com/pulumi/pulumi/issues/5642>

`ConfigFile` is a ComponentResource with sub resources, but the await logic in the Kubernetes provider doesn't know the status of the application of the sub resources.
I'd recommend using kube2pulumi to make the resources in the ConfigFile native resources, and use dependsOn there

this is the issue for it: <https://github.com/pulumi/pulumi-kubernetes/issues/861>

Unfortunately, kube2pulumi does not work with CRDs