Helm-charts: [kube-prometheus-stack] Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com"

[nikosece]

Describe the bug
Error installing prometheus. command -> helm install prometheus prometheus-community/kube-prometheus-stack --namespace monitoring. I got the error

Error: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post "https://prometheus-prometheus-oper-operator.monitoring.svc:443/admission-prometheusrules/mutate?timeout=30s": service "prometheus-prometheus-oper-operator" not found

Althoutgh helm install prometheus stable/prometheus-operator --namespace monitoring was perfectly.
I am using a local kubernetes, at 3 nodes running ubuntu 20.04
Version of Helm and Kubernetes:

Helm Version:

$ helm version
"v3.3.1"

Kubernetes Version:

$ kubectl version
GitVersion:"v1.19.0"

Which chart:
Which version of the chart:

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

<~--
This could be something like:

values.yaml (only put values which differ from the defaults)

key: value

helm install my-release prometheus-community/name-of-chart --version version --values values.yaml

-->

Anything else we need to know:

[bzolivereckle]

same issue here

[robertb724]

Yes, this happens to me as well

[robertb724]

@bzolivereckle @nikosece Are you all installing these charts on the same cluster? I was able to resolve it by deleting the helm release and then deleting the CRDs. After deleting both a fresh install on the new chart is working.

[scottrigby]

Is this issue and fix similar? https://github.com/helm/charts/issues/21080

[smlx]

Is this issue and fix similar? helm/charts#21080

Yes, that is the fix.

I saw this issue when I uninstalled the old prometheus-operator chart from the prometheus-operator namespace and tried to install the new kube-prometheus-stack chart into the kube-prometheus-stack namespace.

Deleting the validatingwebhookconfiguration and mutatingwebhookconfiguration associated with the old prometheus-operator installation fixed this issue for me.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.

[sd2020bs]

same issue, i deleted all old resources(including roles, rolebindins etc) and tried to install :

helm install testmon prometheus-community/kube-prometheus-stack -f values.yaml -n monitoring
and got error:
Error: Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post https://testmon-prometheus-operato-operator.monitoring.svc:443/admission-prometheusrules/mutate?timeout=30s: service "testmon-prometheus-operato-operator" not found

[darkn3rd]

@smlx How do you delete validatingwebhookconfiguration and mutatingwebhookconfiguration. I didn't want to create a new namespace if I can avoid it, because I have an existing name space I would like to use.