Hello Pulumi Community! This is a heads-up announcement regarding a set of bug fixes coming soon to the Pulumi Kubernetes provider (

v4.7.0

). The fixes are related to component option propagation, i.e. how options such as

providers

and

provider

are used by

ConfigFile

,

ConfigGroup

,

Chart

and

Directory

. The gist is that the logic is being standardized across each of the language SDKs, with respect to how the options are set on the child resources based on the provided options. For example. in some SDKs, the

providers

option was ignored. Another example is how

alias

or

ignoreChanges

would be erroneously propagated to the children. Most programs will be unaffected by these fixes, however there's one case where a replacement might occur. In the dotnet SDK, the

ConfigGroup

resource was erroneously setting the child's parent to that of the

ConfigGroup

itself (see issue). Same is true for

ConfigFile

resource. This is now fixed, and Pulumi will automatically fix the parenting relationship, without causing replacement. There is one edge case where replacement would still occur, that's if the provider is different between the

ConfigGroup

and its parent. If you're using the dotnet SDK: to prepare for this change, please review any usage of

ConfigGroup

and of

ConfigFile

, and, if

provider

or

providers

option is used directly, be aware that the child resources may be replaced to have the correct parent. See the PRs for more details: • #2709 Component option propagation (Go SDK) • #2713 Component option propagation (NodeJS SDK) • #2717 Component option propagation (Python SDK) • #2720 Component option propagation (.NET SDK) Thanks and feel free to reach out if you have questions!