I'm running into problems when deploying the prometheus operator to kube via Pulumi. Any ideas on this error?

Previewing update (stack-name):

     Type                                                            Name                                               Plan       Info
     pulumi:pulumi:Stack                                             eks-cluster-online-sandbox
 >-  ├─ pulumi:pulumi:StackReference                                 stack-ref-name    read
     └─ kubernetes:helm.sh:Chart                                     prometheus-operator
 ~      ├─ kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition>  kube-system/prometheusrules.monitoring.coreos.com  update     [diff: ~metadata]
 ~      ├─ kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition>  kube-system/servicemonitors.monitoring.coreos.com  update     [diff: ~metadata]
 ~      ├─ kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition>  kube-system/alertmanagers.monitoring.coreos.com    update     [diff: ~metadata]
 ~      └─ kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition>  kube-system/prometheuses.monitoring.coreos.com     update     [diff: ~metadata]

Resources:
    ~ 4 to update
    95 unchanged

<snip>

Diagnostics:
  kubernetes:<http://apiextensions.k8s.io:CustomResourceDefinition|apiextensions.k8s.io:CustomResourceDefinition> (kube-system/prometheuses.monitoring.coreos.com):
    error: Plan apply failed: 1 error occurred:

    * expected kind, but got map

@early-musician-41645 what’s your CR definition look like?

I didn’t run into the issue previously, will check

I guess this is a problem in our own prometheus chart, we'll dig in to see what the CR definition is

I think so, I’m looking into it

@creamy-potato-29402 I think it was a false alarm, we'll dig in a bit deeper before escalating back

ha, ok