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

It appears we're stumbling over this resource:
<https://github.com/Kong/charts/blob/b87a69dcb92928e228aad59608b439f02ad65f6e/charts/kong/crds/custom-resource-definitions.yaml#L112>

This is the CRD template:
<https://github.com/Kong/charts/blob/main/charts/kong/templates/custom-resource-definitions.yaml>

you can set the resource to be a parent of another resource

<https://gist.github.com/usrbinkat/403321a1f871cbacf3f969e332f7f5ef#file-pulumihelmkonghybrid-md>

```import * as k8s from "@pulumi/kubernetes";

const ns = new k8s.core.v1.Namespace("ns")

const kongGatewayDP = new k8s.helm.v3.Chart("dataplane",{chart: "foo"}, {parent: ns})```

Seems to have worked. I'm still getting attempted duplicate CRD creation but I think I can do a PR against the helm chart repo to fix that (i think)

starting new thread, looks like `--include-crds` is forced at the pulumi level

`const kongGatewayDP = new k8s.helm.v3.Chart("dataplane",{chart: "foo",skipCRDRendering: true}, {parent: ns})`

that got messy fast <https://termbin.com/7mbt>

perhapse I can remove the child resources, then re-deploy them but without the crds

```  parent: kongGatewayCP,```
```  skipCRDRendering: true,```
These two lines of magic from you made my week. Thank you!!