You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using our own monitoring stack. We want to avoid scenarios like when we reinstall Kubesphere, it should not bring back Kubesphere's Prometheus and conflict with our Prometheus deployment.
E0516 18:37:14.984475 1 notification_controller.go:113] get /, Kind= informer error, no matches for kind "Config" in version "notification.kubesphere.io/v2beta1" F0516 18:37:14.984537 1 server.go:339] unable to register controllers to the manager: no matches for kind "Config" in version "notification.kubesphere.io/v2beta1"
kubesphere controller manager goes into crashlooping status because of this error.
We need a reliable method to disable internal Prometheus so we can run external Prometheus without any issues.
The text was updated successfully, but these errors were encountered:
We are using our own monitoring stack. We want to avoid scenarios like when we reinstall Kubesphere, it should not bring back Kubesphere's Prometheus and conflict with our Prometheus deployment.
But when we choose monitoring type as external in the helm chart values
https://github.com/kubesphere/helm-charts/blob/master/src/main/ks-installer/values.yaml#L76 we are facing errors in the fresh Kubesphere deployment.
E0516 18:37:14.984475 1 notification_controller.go:113] get /, Kind= informer error, no matches for kind "Config" in version "notification.kubesphere.io/v2beta1" F0516 18:37:14.984537 1 server.go:339] unable to register controllers to the manager: no matches for kind "Config" in version "notification.kubesphere.io/v2beta1"
kubesphere controller manager goes into crashlooping status because of this error.
We need a reliable method to disable internal Prometheus so we can run external Prometheus without any issues.
The text was updated successfully, but these errors were encountered: