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

<@U05440H8RE3> you are not obliged to use `crd2pulumi`. You can deploy the CRD using our generic <https://www.pulumi.com/registry/packages/kubernetes/api-docs/apiextensions/v1/customresourcedefinition/|CustomResourceDefinition> resource type, or as part of a Helm chart, deployed via <https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/|Chart> or <https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/release/|Release>.
Creating custom resources from it can be done using our generic <https://www.pulumi.com/registry/packages/kubernetes/api-docs/apiextensions/customresource/|CustomResource> resource. Given this is a generic type, it doesn't help you with code assist while writing the custom resources in your code. If you want to let your IDE help you, generating types from your CRDs using `crd2pulumi` allows you to have proper code assist.

Yes, that's correct, I would like to have proper code assist in place for these CRDs. It seems like I will need to invent some automated vendoring solution. It would be nice if popular CRDs were available in the NPM ecosystem (for those using Typescript)

The Pulumiverse community has this repo, but it needs a refresh badly.
<https://github.com/pulumiverse/kubernetes-sdks>