No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

ok I found this:
<https://www.pulumi.com/docs/intro/concepts/programming-model/#resource-providers>
&gt; The resource provider for a custom resource is determined based on its package name. For example, the `aws` package will load a plugin named `pulumi-resource-aws`, and the `kubernetes` package will load a plugin named `pulumi-resource-kubernetes`. Each provider uses the configuration from its package to alter its behavior.
AFAICT "package name" means like `pulumi-kubernetes` i.e. <https://github.com/pulumi/pulumi-kubernetes/> the parent of the `k8s.helm.v2.Chart` from `helm.ts`
so I guess the standard package naming scheme changed since those docs?

And... the point of all this is... a kind of dependency injection?
so in the keda example we're injecting a specific instance of the kubernetes provider, rather than letting `Chart` use the one from <https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/nodejs/provider.ts> which it otherwise would?