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

Not yet, but It’s something we’ve talked about. How would you want to see such a tool work?

i havent looked how they are natively done in go now, so i dont have strong opinions, but if it was something that was easily run as part of a build process to generate them, perfect

we are mostly looking at supporting some of the CRDs related to the prometheus operator <@UH7UWDRC6>

unlikely to change much, but also hate to see a bunch of manual eyeball conversions

Right; I think we’ll create a standalone code-generator tool for that at some point.

In the meantime, easiest approach is probably loading the YAML with ConfigFile/ConfigGroup.

we do it like this but we lose the type checking
```const operatedServiceMonitor = new k8s.apiextensions.CustomResource("prometheus-operated", {
    apiVersion: "<http://monitoring.coreos.com/v1|monitoring.coreos.com/v1>",
    kind: "ServiceMonitor"```


Related: <https://github.com/pulumi/pulumi-kubernetes/issues/219>

<@UGD8LK61H> We also had this question today. Also for `prometheus-operator` parts, esp. `PrometheusRule` for alerts.

<@UH7UWDRC6> At work. Wanted to support that we also stumbled upon this issue.
I didn’t duplicate the question in an extra post, if that’s what you asked for.