autoscaler
autoscaler copied to clipboard
kubernetes
When will the vpa recommender set the recommended value for the vpa's status？
Which component are you using?: vertical-pod-autoscaler
What version of the component are you using?: 0.9.0
Component version:
What k8s version are you using (kubectl version)?:
kubectl version Output
$ kubectl version
What environment is this in?:
What did you expect to happen?:
What happened instead?:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
VPA will set recommendation after it calculates it. If everything is configured correctly (VPA is pointing to an existing controller, there are pods running in the controller, pods are reporting metrics, VPA can get metrics) first recommendation should appear after a few minutes (~1 minute for sample to appear, some time for VPA to get the metric, calculate recommendation and write it).
If this doesn't answer your question then please provide some more context (why are you asking? do you have a VPA object when recommendation doesn't appear as quickly as you'd expect? how long does it take for the recommendation to appear?)
@jbartosik Cannot get ContainerMetricsSnapshot from MetricsClient. Reason: Get "https://172.10.0.1:443/apis/metrics.k8s.io/v1beta1/pods": stream error: stream ID 97; INTERNAL_ERROR
Looks like a log indicating some problem with getting metrics
I can't say anything more just from that, pleas provide some more details.
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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
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:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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.
