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

which I don’t have any issue deleting/installing via `kubectl` myself.

<@UE7AVKHGB> hmm, what version of the kube package are you running?

```"@pulumi/eks": {
      "version": "0.16.6",
      "resolved": "<https://registry.npmjs.org/@pulumi/eks/-/eks-0.16.6.tgz>",
      "integrity": "sha512-yc3ZIyYC74BEf2pW1mRt+j2WJzXwXW16z8XE4/C51xPLJN5J7xQBhDRhh1IaLEA3tmLCRyGXTIUzB6bty9cjdA==",
      "requires": {
        "@pulumi/aws": "^0.16.0",
        "@pulumi/kubernetes": "^0.18.0",
        "@pulumi/pulumi": "^0.16.0",
        "which": "^1.3.1"
      }```

I can try latest version if this is something recently get fixed?

Yup, just delete the code regarding `prometheus-adapter` helm chart installation, and pulumi up to destroy the resource. And do `kubectl api-versions` and you’ll see `<http://v1beta1.custom.metrics.k8s.io|v1beta1.custom.metrics.k8s.io>` is there. While if I do `kubectl delete` then all apis created by the helm chart is deleted.

if so can you file a bug with all the details?

If we can reproduce it we can solve it real quick

I created one: <https://github.com/pulumi/pulumi-eks/issues/67>