Closed tmpbook closed 2 years ago
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
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 and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
Which component are you using?:VPA
What version of the component are you using?:
Component version:0.9.2
What k8s version are you using (
kubectl version
)?:kubectl version
OutputWhat environment is this in?: -
What did you expect to happen?: VPA should take action as the recommendation.
What happened instead?: VPA isn't taking any actions for the recommendation.
How to reproduce it (as minimally and precisely as possible): -
Anything else we need to know?:
kubectl logs vpa-admission-controller-85885bf4b-687zj -nkube-system
Outputkubectl logs vpa-updater-5fdd744d7f-xblq7 -nkube-system
Outputkubectl describe vpa
Output