redhat-cop / resource-locker-operator

Apache License 2.0
30 stars 14 forks source link

Can't install the operator on Kubernetes without PrometheusOperator even though "enableMonitoring=false" #54

Closed Obirah closed 3 years ago

Obirah commented 3 years ago

Hi,

I'm trying to install the resource-locker-operator with Helm on an AWS EKS cluster that has no PrometheusOperator.

I'm using the following command: helm upgrade resource-locker-operator resource-locker-operator/resource-locker-operator --install --set enableMonitoring="false" --namespace resource-locker-operator

With the enableMonitoring flag set to false, I would expect the Helm chart not to try to create a ServiceMonitor, however I get the following error: Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1".

raffaelespazzoli commented 3 years ago

yeah, that feature has not be released. Please be patient, we are planning a release soon (next two weeks).

raffaelespazzoli commented 3 years ago

v1.0.8 contains the change

Obirah commented 3 years ago

Confirmed that it's working with v1.0.8