-
Notifications
You must be signed in to change notification settings - Fork 142
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
VMAgent doesn't work with VPA #693
Comments
Hello! |
The issue at vpa is from us as well. We can't pinpoint the root cause of this issue yet. |
Oh, looks like operator needs to change something here to fit vpa then. |
Hello! Are there any updates on this? seems to effect us |
We also have an issue with this as we have policies in place which checks for existence of a VPA but we cant define a working one. |
Sorry for delay. I think, we should prioritize it. |
* it allows to correctly use VPA controller with vmagent scale sub-resource #693
Fix was added with linked PR. It'll be a part of the next release. Also, I think, that we should add direct support for
Operator is responsible for setting |
Observing metric loss while vmagent scaling. Added hpa on cpu and memory metrics, pods are getting rolled out and observing metric loss. Production clusters are impacted |
Sorry for delay, I think it's related to the kubernetes discovery refresh delay at vmagent side. For proper auto scaling, it's required to set 2 replicas for vmagent and add |
Hello, we are trying to setup a VPA on top of a VMAgent. Unfortunately we get the following error from the VPA
E0718 13:54:51.559558 1 cluster_feeder.go:570] Cannot get target selector from VPA's targetRef. Reason: Unhandled targetRef operator.victoriametrics.com/v1beta1 / VMAgent / application, last error Resource victoria/application has an empty selector for scale sub-resource
Here the manifest of the VPA:
Looking at the CRD of the VMAgent I would expect it to work since
is configured.
Adding another piece to the CRD
shows an empty string.
Any help is appreciated. Maybe we just do something wrong?
The text was updated successfully, but these errors were encountered: