Charts: [stable/prometheus-operator] manifest_sorter.go:192: info: skipping unknown hook: "crd-install" Alertmanager

Created on 30 Mar 2020  ·  22Comments  ·  Source: helm/charts

Describe the bug
Deployment of prometheus-operator fails deployment due to unknown kind Alertmanager, Prometheus and PrometheusRule on monitoring.coreos.com/v1

Version of Helm and Kubernetes:

helm 3.1.2 and Kubernetes v1.15.9-gke.26

Which chart:

Stable release of prometheus-operator version 8.12.3

What happened:
Deployment of chart fails

  manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
  manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
  Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]

What you expected to happen:

Successfully deploy

How to reproduce it (as minimally and precisely as possible):
Deploy the operator using helm3 with the following config and chart version 8.12.3

alertmanager:
  alertmanagerSpec:
    replicas: 3
    podAntiAffinity: soft
    priorityClassName: monitoring

    routePrefix: /alertmanager

    storage:
      volumeClaimTemplate:
        spec:
          accessModes: ["ReadWriteOnce"]
          resources:
            requests:
              storage: 10Gi
        selector: {}

prometheusOperator:
  cleanupCustomResource: true
  configReloaderCpu: 300m
  tlsProxy:
    enabled: false
  admissionWebhooks:
    enabled: false

Anything else we need to know:

I've tried with and without helmfile v0.106.3 with helm-diff 3.1.1

lifecyclstale
Source
picture rchenzheng
👍9

Most helpful comment

still an issue

picture PaulCharlton on 11 Aug 2020
👍22

All 22 comments

I have the exact same issue, running helm 3.1.2 and prometheus-operator: 8.12.3.

This error has been seen before and fixed, yet it appeared again. Probably due to the CRD not installed first. There is a workaround on fetching the CRD manifests and installing them first, then running the helm install again (while disabling crd installation using the values.yaml).

LordNoteworthy picture LordNoteworthy on 1 Apr 2020

Can anyone please have a look here?

I retried with helm v3.2.0, deploying latest prometheus-operator:8.13.2 still gives this problem.

manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
Error: UPGRADE FAILED: [unable to recognize "": no matches for kind "Alertmanager" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "PrometheusRule" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]

Even if installing the CRD before, I still get a lot of conflicts of ServiceAccount and PodSecurityPolicy :( like:

Error: UPGRADE FAILED: rendered manifests contain a new resource that already exists. Unable to continue with update: existing resource conflict: namespace: , name: andromeda-grafana, existing_kind: policy/v1beta1, Kind=PodSecurityPolicy, new_kind: policy/v1beta1, Kind=PodSecurityPolicy

LordNoteworthy picture LordNoteworthy on 27 Apr 2020

You can view README.md
[https://github.com/helm/charts/blob/master/stable/prometheus-operator/README.md]

Prerequisites

wzm74110 picture wzm74110 on 30 Apr 2020
👎22

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] picture stale[bot] on 30 May 2020

This issue is being automatically closed due to inactivity.

stale[bot] picture stale[bot] on 13 Jun 2020

still an issue

PaulCharlton picture PaulCharlton on 11 Aug 2020
👍22

Issue is still there.
helm version
version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"dirty", GoVersion:"go1.14.3"}

Error:
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"

texanraj picture texanraj on 13 Aug 2020
👍12

Having this issue as well. Steps to reproduce: 

k3d cluster stop testcluster
helm install prometheus-operator stable/prometheus-operator

Output of helm install: 

❯ helm install prometheus-operator stable/prometheus-operator
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
NAME: prometheus-operator
LAST DEPLOYED: Wed Aug 26 15:50:16 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
The Prometheus Operator has been installed. Check its status by running:
  kubectl --namespace default get pods -l "release=prometheus-operator"

Visit https://github.com/coreos/prometheus-operator for instructions on how
to create & configure Alertmanager and Prometheus instances using the Operator.
helm install prometheus-operator stable/prometheus-operator  10.04s user 1.47s system 38% cpu 30.231 total
davidcorbin picture davidcorbin on 26 Aug 2020

Installed today on a fresh eks cluster v1.16
Same issue as reported by @davidcorbin

On Helm3 version.BuildInfo{Version:"v3.2.0", GitCommit:"e11b7ce3b12db2941e90399e874513fbd24bcb71", GitTreeState:"clean", GoVersion:"go1.13.10"}

webmutation picture webmutation on 1 Sep 2020

Having the same problem. Probably worth opening a new issue since this one was closed "due to inactivity". (And then people wonder why +1 comments are so popular, as long as you are going to close issues due to inactivity you have to embrace the +1 comments)

version.BuildInfo{Version:"v3.3.1", GitCommit:"249e5215cde0c3fa72e27eb7a30e8d55c9696144", GitTreeState:"clean", GoVersion:"go1.14.7"}

Kubernetes v1.18.8

helm install r1 stable/prometheus-operator
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
NAME: r1
LAST DEPLOYED: Thu Sep  3 10:36:19 2020
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
The Prometheus Operator has been installed. Check its status by running:
  kubectl --namespace default get pods -l "release=r1"

Visit https://github.com/coreos/prometheus-operator for instructions on how
to create & configure Alertmanager and Prometheus instances using the Operator.
AndrewSav picture AndrewSav on 3 Sep 2020
👍9

I'm seeing the same messages on helm install:
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
...repeated a total of 6 times.

It does seem to successfully create the CRDs, however.

Versions:
Chart: prometheus-operator-9.2.2
App: 0.38.1

Helm: version.BuildInfo{Version:"v3.2.1", GitCommit:"fe51cd1e31e6a202cba7dead9552a6d418ded79a", GitTreeState:"clean", GoVersion:"go1.13.10"}

Kubernetes: 

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:30:10Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976", GitCommit:"4c6976793196d70bc5cd29d56ce5440c9473648e", GitTreeState:"clean", BuildDate:"2020-07-17T18:46:04Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
deleted picture deleted on 4 Sep 2020

good idea @AndrewSav . Please open new ticket reference this so people can link the two!

webmutation picture webmutation on 4 Sep 2020

Can confirm, still an issue (using k3s)

$ helm install prometheus stable/prometheus-operator --namespace monitoring

manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
NAME: prometheus
LAST DEPLOYED: Tue Sep 8 10:15:41 2020
NAMESPACE: monitoring
STATUS: deployed
REVISION: 1
NOTES:
The Prometheus Operator has been installed. Check its status by running:
kubectl --namespace monitoring get pods -l "release=prometheus"

Visit https://github.com/coreos/prometheus-operator for instructions on how
to create & configure Alertmanager and Prometheus instances using the Operator.

TheJaySmith picture TheJaySmith on 8 Sep 2020
👍5

Can confirm. Still an issue with EKS 1.16.

arvin6msd picture arvin6msd on 10 Sep 2020
👍3

I'm getting this error using kind too. Below are my specs in case they are useful

$ helm version
version.BuildInfo{Version:"v3.3.4", GitCommit:"a61ce5633af99708171414353ed49547cf05013d", GitTreeState:"dirty", GoVersion:"go1.15.2"}

$ kind version
kind v0.9.0 go1.15.2 darwin/amd64



md5-7e371fcd2f026ccffe1ca5d28ebdfd23



$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.6-beta.0", GitCommit:"e7f962ba86f4ce7033828210ca3556393c377bcc", GitTreeState:"clean", BuildDate:"2020-01-15T08:26:26Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-14T07:30:52Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
hielfx picture hielfx on 25 Sep 2020

I can confirm still an issue with v1.17.11-eks-cfdc40

hbceylan picture hbceylan on 7 Oct 2020
👍3

confirm issue with v1.18.8 & helm "v3.3.4"

dbaskakov picture dbaskakov on 26 Oct 2020

Confirmed on K8s 1.19.3 and Helm 3.2.4

mathias-ewald picture mathias-ewald on 28 Oct 2020

k8s 1.19.3 & helm 3.3.0 - still an issue

ghudgins picture ghudgins on 1 Nov 2020

While everyone is reporting this problem, the issue is closed 🤷‍♂️

mathias-ewald picture mathias-ewald on 3 Nov 2020
😄3

While everyone is reporting this problem, the issue is closed 🤷‍♂️

Probably because it's deprecated and the moved on to https://github.com/prometheus-community/helm-charts, maybe it's been fixed on newer versions

rchenzheng picture rchenzheng on 3 Nov 2020

see https://github.com/prometheus-community/helm-charts/issues/155

bergerx picture bergerx on 6 Nov 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

rajkumar49 picture rajkumar49  ·  3Comments
vsliouniaev picture vsliouniaev  ·  3Comments
harshmehta93 picture harshmehta93  ·  3Comments
mluedke picture mluedke  ·  3Comments
kminehart picture kminehart  ·  3Comments