Eron Wright

To summarize, there's various ways to (inadvertently) have two Pulumi resources pointing to the same Kubernetes object. Whether by changing the type of resource (e.g. `Chart` to `Release`) or the...

A fix is under development in pu/pu for how resource reference outputs are handled: https://github.com/pulumi/pulumi/pull/15795/commits/8cd0a87cd7294ed10bc86112b29ea2a00451a1ed Also a `pulumi.json/#Resource` schema type will be introduced, such that the `resources` output property have...

Here's what happened in my case: the provider was sent a `Cancel` RPC, causing the provider's internal context to be canceled. In subsequent requests, the kube client logic is the...

https://github.com/pulumi/pulumi-hugo/pull/4043

https://www.pulumi.com/blog/kubernetes-yaml-v2/

Related: - https://github.com/pulumi/pulumi-kubernetes/pull/946 - https://github.com/pulumi/pulumi-kubernetes/pull/960 - https://github.com/pulumi/pulumi-kubernetes/pull/1255 - https://github.com/pulumi/pulumi-kubernetes/pull/1886 - https://github.com/pulumi/pulumi-kubernetes/pull/1733

Reopening this because the PR was reverted.

Folks, I am re-opening this issue to have a conversation about an unforeseen consequence, which is that Pulumi's behavior has diverged from that of Helm. The behavior of `helm install`...

A good workaround for this is to use the `com.pulumi.kubernetes.yaml.v2.ConfigGroup` resource (new in v4.10), specifically the `objs` property since it accepts object literals. The effect is similar to creating a...

Since https://github.com/pulumi/pulumi-kubernetes/pull/2672 the provider looks to the `version` within `Chart.yaml` to determine whether the local chart has substantively changed (thus triggering an upgrade). Imagine that the provider simply ignored the...