-
Notifications
You must be signed in to change notification settings - Fork 550
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
Support secondary custom-metric-server #522
Comments
@dgrisonnet any suggestions? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
This is a feature that would be very useful, but it shouldn't be done at the prometheus-adapter level since we don't have the resources today to invest into that. As such I am denying this feature request. But we could benefit from the more general effort in kubernetes-sigs/custom-metrics-apiserver#70. |
ok, We know users that have more than one custom metric servers, it should be a way to resolve it. |
As we know, k8s don't support multiple custom-metric-server in one cluster :kubernetes-sigs/custom-metrics-apiserver#70
One possible solution is to build an CRD for metric routing. But, it's too complicated for mostly of the users. Most of the time we just have two custom-metric-server in one cluster, So how about let prometheus-adapter support a secondary custom-metric-server.
The configuration is like this:
the logic for handle a metric would be:
If it is needed, I want to implement it.
The text was updated successfully, but these errors were encountered: