Eron Wright

Let me state my opinion here, that Kubernetes SSA is designed for a multi-party authoring experience (where multiple parties apply their intentions to a given object), but design-wise says nothing...

I'm reassigning to Bryce since he's working on #2745 and that should resolve this one.

To summarize the issue and its connection to #1253, the `TagAtScope` resource assumes that it totally manages the tags of the target resource, and [complains](https://github.com/pulumi/pulumi-azure-native/blob/5bf7f2340be2cfb2b73d53301f75b0a940d5dc3f/provider/pkg/azure/client_azcore.go#L430) if there are existing tags...

To set the tags on a managed resource group, I would recommend doing that on the `ResourceGroup` itself. See also https://github.com/pulumi/pulumi-azure-native/issues/4196 for why you shouldn't use `TagAtScope` if you own...

Checked with @pierskarsenbarg, we think the use case here is being able to non-exclusively add tags to a given scope. The `TagAtScope` resource today takes total ownership of the tags,...

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, and effectively decouples...

I opened a PR to simply increase the default recursion limit, as a reasonable workaround: https://github.com/protocolbuffers/protobuf/pull/17881

Thanks @ajwtech for the report and for the workaround. We'll add this to our backlog.

Thinking about possible designs, a key question would be how to attach policies to stacks, i.e. to form a policy group. Since policies are normally enforced by an administrator, it...

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