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

Try CRD
<https://www.pulumi.com/registry/packages/kubernetes/api-docs/apiextensions/customresource/>

Is that the only option? I thought it used to be possible to send a raw manifest but can’t seem to find it in the docs anymore

you can use yaml file - <https://www.pulumi.com/registry/packages/kubernetes/api-docs/yaml/configfile/>

CDR will be nicer, too bad their CRD definition does not define anything for the spec bit <https://github.com/openshift/router/blob/master/deploy/route_crd.yaml>

spec is pretty much an anonymous object that you can pass in any form. There is no compile time validation unfortunately, but I am sure you can define it externally and be good with it

yeah, making my own type in the generated code

Perhaps the Pulumi team can think of making the CustomResource class generic to make typings easier

<@U01LHRC2M8T> we have crd2pulumi already

FYI, you can also use <https://www.pulumi.com/registry/packages/kubernetes/api-docs/apiextensions/customresource/|CustomResource> to define the specs