-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
[vpa] Documentation for configuration options #3784
Comments
We do not have up to date documentation of the parameters (I suppose it would get out of date very quickly, bt you can run the binary with the --help option to get the flag description. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Please could we get more complete documentation on setting up Prometheus as a history provider for the VPA recommender component? For example how to customize it and verify that it is indeed working? Also including whether CPU and memory queries are customizable or not? It would be nice if the documentation could include which jobs get queried e.g. is it the "kubernetes-nodes-cadvisor" and "kubernetes-pods", just the one, or are there more? Running the previously recommended command:
The descriptions of these options are too similar i.e. "Label name to look for container names"... are they all looking for container names (or is one looking for pod names)?... are they used in conjunction or either/or? :
I'm having trouble wrapping my head around when above and below options should be used:
Would it be possible to provide examples and/or elaborate on all of the above? |
Here are some instances where such docs might have helped:
|
/remove-lifecycle rotten |
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 |
I am / we are absurdly grateful for this project and the value it provides, having used it extensively over the last few years, but after fighting the prometheus integration setup for the first time ever for awhile last night I agree with this. It is rather obtuse trying to figure out what is going on with these options and requires a detailed analysis of the underlying codebase. Even after doing so, I wasn't successful. It also isn't super clear what happens to the existing checkpoints when migrating storage backends and what behavior one can expect to occur in this process, which is a bit scary given that we've already littered our production environment with VPA. My fragile understanding thus far:
Is that all accurate? I tried using the kube-state-metrics
|
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. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Which component are you using?:
VPA recommender.
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
Better user experience and easier debugging.
Describe the solution you'd like.:
Documentation for these VPA recommender configuration options:
Granted, some of these are pretty self-explanatory, but some of not obvious. For example, the
pod-label-prefix
configuration option - how is that used and do I need to configure it? I know other people might think that, because I certainly did. Users shouldn't have to dig through the code in order to understand what they do.Describe any alternative solutions you've considered.:
Little to no documentation, as it stands now - I feel like that's not an ideal scenario.
The text was updated successfully, but these errors were encountered: