Matthew (Matt) Jeffryes

Thanks for filing this @blaargh. As indicated in the docs for [kubernetes.helm.sh.v3.Chart | Pulumi Registry](https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#depend-on-a-chart-resource); using `dependsOnInputs` with `chart.Ready` is the recommended approach. Unfortunately, I think the issue here is...

Thanks for the issue @awopenphone; could you elaborate a bit on this request to give context? What was the name of the option that was removed in v4.7.0?

Thanks for reporting this @sebastien-prudhomme and for sharing your workaround. This is an awkward usability issue, we'll keep investigating to see if we can improve it.

Thanks @adriangb; yes, while the `CustomResource` resource type accepts arbitrary input fields, only the `apiVersion` `kind` and `metadata` input properties are copied to the output. You could potentially work around...

Glad that workaround worked for you. I did some digging on whether we can make the typing better here, and it seems we're a little hamstrung by the fact that...

Thanks for the bug report and for sharing your workaround @patrickli. We'll look into why the type definitions are not matching the docs here.

As noted on #2948, the upsert behavior can also cause pulumi to silently delete a resource the user was intending to rename

Thanks for pointing this out @tedvanderveen; we'll try to get this on the roadmap.

Thanks for the bug report @servcoben From the trace it seems like the offending line is probably about here: https://github.com/pulumi/pulumi-kubernetes/blob/53f0563ecc4df9c185222c75bebda179f5b743ec/sdk/dotnet/Yaml/Yaml.cs#L1038C22-L1038C27 My best guess is that somehow the provider config is...

Thanks for the bug report @Alwin-Stockinger; it looks like that crd specifies a default for an object (`EC2NodeClassSpec/properties/metadataOptions`) you should be able to workaround by removing the default lines here:...