Eron Wright

The `get` functions are mainly designed to retrieve a single resource. For example, it is possible to get a specific node by name (in this case, the node named `docker-desktop`):...

Possible duplicate: https://github.com/pulumi/pulumi-kubernetes/issues/2034

@chirauki could you answer some clarifying questions? 1. Do you have an example of a thirty-party controller that would have a problem with how Pulumi deletes resources? 2. When you...

I do have a theory on how foreground deletion could be a problem for some controllers: With foreground cascading deletion, the controller must be careful to not finalize the object...

This error represents a failure to lookup the `ExternalSecret` CRD in the Kubernetes cluster, in using `v2.ConfigGroup` or `v2.ConfigFile`. I think you may have hit upon a limitation that we'll...

I would suggest using `Release` resource as a workaround for now. It is effective because previews of a `Release` doesn't perform a dry-run. Even if roles were created before bindings,...

I see two possible improvements here: 1. In preview, use client-side validation only for bindings, no server-side dry-run. 2. Enhance the ordering logic to create roles before bindings, to avoid...

@ChristianRaoulis I notice that the resource URN has an unusual value: ``` urn:pulumi:testing::softwarefactory::kubernetes:core/v1:Namespace$softwarefactory:rabbitmq$kubernetes:helm.sh/v3:Chart$kubernetes:rbac.authorization.k8s.io/v1:RoleBinding::core-services/rabbitmq-endpoint-reader ``` It seems like a `core-services` namespace resource is involved, and maybe being used as a parent?...

I would advocate for fail-fast behavior with any kind, not just namespace.

Another variation: https://github.com/pulumi/pulumi-kubernetes/issues/2227#issuecomment-1482511794