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

<@UV8MYJPQA> would you mind sharing what your problem and solution was?

Well, honestly, it's more of a workaround than an actual fix but for now, I disabled all the `ServiceMonitor` resources from the graph as I found in this other pulumi ticket dealing with the same issues I was having (<https://github.com/pulumi/pulumi-kubernetes/issues/285>)

So now my call to the chart looks like
```  const prometheus = new k8s.helm.v2.Chart("po", {
    chart: 'prometheus-operator',
    repo: 'stable',
    version: '8.12.1',
    transformations: [removeGrafanaTest, addNamespace(monitoringNamespaceName)],
    namespace: monitoringNamespaceName,
    values: {
      kubeControllerManager: { enabled: false },
      kubeEtcd: { enabled: false },
      kubeScheduler: { enabled: false },
      kubeProxy: {enabled: false},
      coreDns: { enabled: false },
      prometheusOperator: { createCustomResource: false }
    }
  }
}```

and that has at least resulted in things coming up and producing metrics for the entire cluster

ultimately though, we'd like to have those service monitors working...