helm / charts

⚠️(OBSOLETE) Curated applications for Kubernetes
Apache License 2.0
15.49k stars 16.83k forks source link

[stable/prometheus-operator] issue using crdApiGroup #17162

Closed allamand closed 4 years ago

allamand commented 5 years ago

Hello,

I'm deploying with prometheus-operator-6.8.1 and App=0.32.0 and changing the name of the crdApiGroup:

helm install --namespace monitoring-seb --name prometheus-monitoring-seb -f samples/prometheus-values.yaml stable/prometheus-operator --set prometheusOperator.crdApiGroup=monitoring.seb --set prometheusOperator.createCustomResource=false

All the CRDs are correctly created and when running this, the Prometheus operator Pod will Crash with thoses logs :

ts=2019-09-16T14:11:06.497975663Z caller=main.go:187 msg="Starting Prometheus Operator version '0.32.0'."
ts=2019-09-16T14:11:06.505429026Z caller=main.go:95 msg="Staring insecure server on :8080"
level=info ts=2019-09-16T14:11:06.60911869Z caller=operator.go:425 component=prometheusoperator msg="connection established" cluster-version=v1.14.3
level=info ts=2019-09-16T14:11:07.596856487Z caller=operator.go:222 component=alertmanageroperator msg="connection established" cluster-version=v1.14.3
level=info ts=2019-09-16T14:11:08.09755298Z caller=operator.go:1599 component=prometheusoperator msg="CRD updated" crd=Prometheus
level=info ts=2019-09-16T14:11:08.144704333Z caller=operator.go:1599 component=prometheusoperator msg="CRD updated" crd=ServiceMonitor
level=info ts=2019-09-16T14:11:08.198191887Z caller=operator.go:1599 component=prometheusoperator msg="CRD updated" crd=PodMonitor
level=info ts=2019-09-16T14:11:08.272317527Z caller=operator.go:1599 component=prometheusoperator msg="CRD updated" crd=PrometheusRule
level=info ts=2019-09-16T14:11:08.510920735Z caller=operator.go:644 component=alertmanageroperator msg="CRD updated" crd=Alertmanager
ts=2019-09-16T14:11:11.27461747Z caller=main.go:303 msg="Unhandled error received. Exiting..." err="creating CRDs failed: waiting for Prometheus crd failed: timed out waiting for Custom Resource: failed to list CRD: prometheuses.monitoring.coreos.com is forbidden: User \"system:serviceaccount:monitoring-seb:prometheus-monitoring-seb-operator\" cannot list resource \"prometheuses\" in API group \"monitoring.coreos.com\" at the cluster scope"

In the logs we see that prometheus is looking for API Group monitoring.coreos.com but this should be monitoring.seb as I ask to deploy with a different name.

How can I tell prometheus operator to uses the crd with the name I specified ?

thanks

stale[bot] commented 4 years ago

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.

allamand commented 4 years ago

This is real issue can someone take a look ?

stale[bot] commented 4 years ago

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] commented 4 years ago

This issue is being automatically closed due to inactivity.