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
Error's creating crd's #78
Comments
Hello, Can you try to install latest release? v0.2.0. It seems like you're using old version and kubernetes 1.18 You can download new release with bundle: https://github.com/VictoriaMetrics/operator/releases/download/v0.2.0/bundle_crd.zip Or use kustomize from quick-start docs: https://github.com/VictoriaMetrics/operator/blob/master/docs/quick-start.MD#installing-by-kustomize Soon we'll also introduce helm chart. |
Hi, Thank you very much for response. I managed to install operator, thank you. However, when I am trying to create any of objects, kubectl shows that those are created but nothing in the cluster is appeared though. Operator logs show this:
More recent log here - http://paste.openstack.org/show/797247/ Nevertheless, I ve added prometheus crd's from here https://github.com/helm/charts/tree/master/stable/prometheus-operator#helm-fails-to-create-crds |
Thanks for the report, i'v managed to find an issue with rbac. It was fixed at master branch, but it wasn't included at v0.2.0 release. Without properly configured rbac - operator wasn't able to start items reconciliation. For now you can solve the problem with two options:
Btw, if you dont have prometheus operator crd, you can disable converter by setting following env variables to the operator deployment
|
Thanks a lot, it worked. I have one more question - in quick start docs, everything is showed in conjunction with vmsingle deployment of victoriametrics. However, I am a bit confused how can I use those tools (like vmagent, vmalert, etc) with VMcluster deployment? I ve found some referal to that https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/app/vmagent#splitting-data-streams-among-multiple-systems ; but I am still not getting how can you specify remoteWrite to ClusterIP's of VMcluster. I ve tried vminstert but it doesnt seem like the right way |
Great! We have separate article for High-Availability setup link. |
Hey folks, I am having a similar experience while trying to get VMAlert up-and-running. My rbac includes the vmsingles update and I have added the ServiceMonitor, PodMonitor, PrometheusRule, and probe CRD's to my manifests. All the errors cleared from my vm-operator logs EXCEPT for probes.
The last line just repeats forever and I am wondering if this is my blocker to why my alertmanager isn't being notified. Any guidance is greatly appreciated! Thanks |
Hello, @FHIR360 , according to log file, You can check it by executing commands: kubectl -n default get deploy
kubectl -n default get pods Let me know, if it doesnt help. |
Thank you very much, @f41gh7 , definitely a major issue in my implementation! |
@FHIR360 close an issue, feel free to reopen if any question |
Hi,
The text was updated successfully, but these errors were encountered: