Prometheus 运算符`"alertmanagers.monitoring.coreos.com" 已经存在`
Prometheus Operator `"alertmanagers.monitoring.coreos.com" already exists`
这是一个默认值，一个全新的，否则是空的 minikube。我怀疑有什么东西坏了？
仅供参考，我尝试回滚到 Kubernetes v1.12.3，但我得到了相同的错误结果。
~ minikube delete
Deleting local Kubernetes cluster...
Machine deleted.
~ rm -rf ~/.helm
~ minikube start --memory 8000 --kubernetes-version v1.13.0
Starting local Kubernetes v1.13.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
~ eval $(minikube docker-env)
~ helm init
helm init
Creating /Users/myname/.helm
Creating /Users/myname/.helm/repository
Creating /Users/myname/.helm/repository/cache
Creating /Users/myname/.helm/repository/local
Creating /Users/myname/.helm/plugins
Creating /Users/myname/.helm/starters
Creating /Users/myname/.helm/cache/archive
Creating /Users/myname/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /Users/myname/.helm.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
~ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
~ helm install --name myprometheus stable/prometheus-operator
Error: release myprometheus failed: customresourcedefinitions.apiextensions.k8s.io "alertmanagers.monitoring.coreos.com" already exists
我从 helm 2.12.0 回滚到 2.11.0，错误消失了，prometheus-operator 恢复了工作。新的 Helm 2.12.0 和 prometheus-operator 之间似乎存在一些不兼容性。我想这会及时得到解决。
这是一个默认值，一个全新的，否则是空的 minikube。我怀疑有什么东西坏了？
仅供参考，我尝试回滚到 Kubernetes v1.12.3，但我得到了相同的错误结果。
~ minikube delete
Deleting local Kubernetes cluster...
Machine deleted.
~ rm -rf ~/.helm
~ minikube start --memory 8000 --kubernetes-version v1.13.0
Starting local Kubernetes v1.13.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Setting up certs...
Connecting to cluster...
Setting up kubeconfig...
Starting cluster components...
Kubectl is now configured to use the cluster.
Loading cached images from config file.
~ eval $(minikube docker-env)
~ helm init
helm init
Creating /Users/myname/.helm
Creating /Users/myname/.helm/repository
Creating /Users/myname/.helm/repository/cache
Creating /Users/myname/.helm/repository/local
Creating /Users/myname/.helm/plugins
Creating /Users/myname/.helm/starters
Creating /Users/myname/.helm/cache/archive
Creating /Users/myname/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /Users/myname/.helm.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
~ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
~ helm install --name myprometheus stable/prometheus-operator
Error: release myprometheus failed: customresourcedefinitions.apiextensions.k8s.io "alertmanagers.monitoring.coreos.com" already exists
我从 helm 2.12.0 回滚到 2.11.0，错误消失了，prometheus-operator 恢复了工作。新的 Helm 2.12.0 和 prometheus-operator 之间似乎存在一些不兼容性。我想这会及时得到解决。