Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubesphere external monitoring type setting in values file is not working #234

Open
KR411-prog opened this issue May 16, 2022 · 0 comments

Comments

@KR411-prog
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant