Matthew (Matt) Jeffryes

I'm pretty confident changing the behavior of capturing `KUBECONFIG` would be breaking (even if it only affects explicit providers), because there may be users implicitly relying on this behavior. A...

Thanks for filing this issue @yotamm; it looks like this would require a breaking change to fix so we'll track it to try to include in the next major version...

Thanks for the detailed write up @gunzy83. This behavior is indeed a product of the new refresh diff behavior introduced in https://github.com/pulumi/pulumi/pull/16146. That change was intentionally limiting the scope of...

> Thinking back, the weirdest case was when I imported resources, then the resources in program did not include all the labels in the resource in the cluster. The diff...

thanks for the issue report @geowalrus4gh; it migyht be helpful to compare the version of the `pulumi-yaml` plugin that's being used locally vs in the operator.

Related [Default NodeSecurityGroup does not work with ipv6· pulumi-eks/1700](https://github.com/pulumi/pulumi-eks/issues/1700), [IPv6 clusters break because of netmask dependency in YAML· pulumi-eks/1520](https://github.com/pulumi/pulumi-eks/issues/1520)

This is probably due to us setting a default on this config here: https://github.com/pulumi/pulumi-azure/blob/master/provider/resources.go#L561

Thanks for reaching out @timkelley-ingage. In order to be able to help you, we're going to need more information. Does this issue reproduce consistently? If so, can you share the...