Eron Wright

Shall I change the default in the other languages too, for consistency? Was seeking to minimize scope but have no other objection.

Related: https://github.com/pulumi/pulumi-kubernetes-operator/issues/447

@blampe this ticket seems vague, and we did some e2e test work after it was filed. Would you rework it or close it?

Some docs were added along these lines: https://github.com/pulumi/docs/commit/9da1943043145b75e547da56e9e1016b8bef7885

I would advocate for an approach that would allow for MLC component debugging, in addition to program debugging. The whole idea of pivoting to "running programs directly" doesn't solve for...

The problem appears to be fixed, the provided program works as expected. ```plain + kubernetes:apps/v1:Deployment: (create) [urn=urn:pulumi:dev2::issue-1396-dotnet::kubernetes:helm.sh/v3:Chart$kubernetes:apps/v1:Deployment::kube-system/kubernetes-dashboard] [provider=urn:pulumi:dev2::issue-1396-dotnet::pulumi:providers:kubernetes::default_4_9_1::04da6b54-80e4-46f7-96ec-b56ff0331ba9] apiVersion: "apps/v1" kind : "Deployment" metadata : { labels : { app.kubernetes.io/component...

Good news everyone, we just release a preview of Pulumi Kubernetes Operator v2. This new release has a whole-new architecture that uses pods as the execution environment. The program sources...

My understanding of this enhancement request is to provide a manual re-sync trigger, i.e. `pulumi up` on demand. Good news is that the `pulumi.com/reconciliation-request` annotation is [understood](https://github.com/pulumi/pulumi-kubernetes-operator/issues/672#issuecomment-2364665802) to have the...

@blampe I'm closing this PR in favor of different solution(s), e.g. - https://github.com/pulumi/pulumi-kubernetes/issues/3299 - https://github.com/pulumi/pulumi-kubernetes/issues/3300

The az-native provider does have support for propagating the auto-name e.g. to sub-resources. I take this to be a bug that the name is not propagating in this case. Refs:...