Charts: kube-prometheus fails with unknown fields

[MrAmbiG]

Which chart:
kube-prometheus

Describe the bug

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"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(Prometheus.spec): unknown field "probeNamespaceSelector" in com.coreos.monitoring.v1.Prometheus.spec, ValidationError(Prometheus.spec): unknown field "probeSelector" in com.coreos.monitoring.v1.Prometheus.spec]

To Reproduce
Steps to reproduce the behavior:
helm repo add bitnami https://charts.bitnami.com/bitnami
helm -n monitoring install prometheus bitnami/kube-prometheus

Expected behavior
It gets installed

Version of Helm and Kubernetes:

• Output of helm version:

v3.3.1

• Output of kubectl version:

v1.19.2

Additional context
It seems that the child charts on which the parent chart depends on is not referring to the child chart values correctly. I did try to download the chart, do a helm dep up and then try to install it but same error.

[juan131]

Hi @MrAmbiG

I am unable to reproduce the issue:

$ helm search repo bitnami/kube-prometheus
NAME                    CHART VERSION   APP VERSION DESCRIPTION
bitnami/kube-prometheus 2.2.1           0.42.1      kube-prometheus collects Kubernetes manifests t...
$ kubectl create ns monitoring
namespace/monitoring created
$ helm -n monitoring install prometheus bitnami/kube-prometheus
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"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
NAME: prometheus
LAST DEPLOYED: Mon Oct 19 09:31:57 2020
NAMESPACE: monitoring
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
** Please be patient while the chart is being deployed **

Watch the Prometheus Operator Deployment status using the command:

    kubectl get deploy -w --namespace monitoring -l app.kubernetes.io/name=kube-prometheus-operator,app.kubernetes.io/instance=prometheus

Watch the Prometheus StatefulSet status using the command:

    kubectl get sts -w --namespace monitoring -l app.kubernetes.io/name=kube-prometheus-prometheus,app.kubernetes.io/instance=prometheus

Prometheus can be accessed via port "9090" on the following DNS name from within your cluster:

    prometheus-kube-prometheus-prometheus.monitoring.svc.cluster.local

To access Prometheus from outside the cluster execute the following commands:

    echo "Prometheus URL: http://127.0.0.1:9090/"
    kubectl port-forward --namespace monitoring svc/prometheus-kube-prometheus-prometheus 9090:9090

Watch the Alertmanager StatefulSet status using the command:

    kubectl get sts -w --namespace monitoring -l app.kubernetes.io/name=kube-prometheus-alertmanager,app.kubernetes.io/instance=prometheus

Alertmanager can be accessed via port "9093" on the following DNS name from within your cluster:

    prometheus-kube-prometheus-alertmanager.monitoring.svc.cluster.local

To access Alertmanager from outside the cluster execute the following commands:

    echo "Alertmanager URL: http://127.0.0.1:9093/"
    kubectl port-forward --namespace monitoring svc/prometheus-kube-prometheus-alertmanager 9093:9093

What version of the kube-prometheus chart are you using?

[stale[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[BenjaminWie]

I used the following version and got the same error:
bitnami/kube-prometheus 2.2.4 0.43.2 kube-prometheus collects Kubernetes manifests t...
helm version: 3.4
kubernetes version

[FraPazGal]

Hi @BenjaminWie,

Are you encountering the issue at installation time? Please share with us the complete logs of the error and any custom values you used, if any.

[AndrzejOlender]

I had the same problem today, I had to remove the old CRDs

kubectl delete crd alertmanagerconfigs.monitoring.coreos.com
kubectl delete crd alertmanagers.monitoring.coreos.com
kubectl delete crd podmonitors.monitoring.coreos.com
kubectl delete crd probes.monitoring.coreos.com
kubectl delete crd prometheuses.monitoring.coreos.com
kubectl delete crd prometheusrules.monitoring.coreos.com
kubectl delete crd servicemonitors.monitoring.coreos.com
kubectl delete crd thanosrulers.monitoring.coreos.com

[FraPazGal]

Hi @AndrzejOlender,

Thank you for your input! It is possible that old CDRs are left after helm install which could create issues with a new installation. @BenjaminWie, could you try and see if this solution works for you?

[BenjaminWie]

Thanks @AndrezjOlender - this solved the problem on my side