This message was deleted.

@dry-keyboard-94795 the

yaml.ConfigFile

is in Pulumi speak a single resource, so that get’s provisioned using a single k8s provider. For a component, where you can mix resources from multiple providers, you have to pass the

providers

collection. There is no need to pass this collection to the child resources if you set the component resource as the

parent

in the child resource. Provider lookup traverses the

parent

links to find a provider. See the documentation page on

parent

for more info: https://www.pulumi.com/docs/intro/concepts/resources/options/parent/

Yep, we use the parent option. We're using a global ResourceOptions object, which we went changed to use

providers

as we added a component resource. Unfortunately, it looks like the ConfigFile resource depends on

provider

being passed explicitly to it. I've opened a github issue for it since with more details