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

we've heard this before. can you share the exact call to helm.v2.chart

in previous instances of this problem it has been the case that the chart has generated two of the same crd. that issue should have been fixed though

this is my index.ts:
```import * as k8s from "@pulumi/kubernetes";
import * as config from './config';

function addNamespace(o: any) {
    if (o !== undefined) {
        o.metadata = Object.assign(o.metadata || {}, {namespace});
    }
}

const namespace = config.namespace;

if (namespace !== 'default') {
    new k8s.core.v1.Namespace("testrandom0x112", {
        metadata: {
            name: namespace
        }
    }, {
        provider: config.k8sProvider
    });
}

const prometheus_operator2 = new k8s.helm.v2.Chart(
    "prometheus-operator2", 
    {
        repo: "stable",
        chart: "prometheus-operator",
        version: "4.2.1",
        namespace,
        values: {
            replicaCount: 1
        },
        transformations: [addNamespace]
    },
    { providers: { kubernetes: config.k8sProvider } },
);```

cc <@UE1LN7A22> I'm not back until 1 or so

my colleague looked deeper, added more conditions to the addNamespace function in index.ts to get around this issue

I believe this is another instance of <https://github.com/pulumi/pulumi-kubernetes/issues/456>