We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Which component are you using?:
vertical-pod-autoscaler
What version of the component are you using?:
Component version: 0.14.0
What k8s version are you using (kubectl version)?:
kubectl version
$ kubectl version
What environment is this in?:
AWS EKS / k3d local cluster
What did you expect to happen?:
sharedIndexInformer not started more than once
What happened instead?:
Seven sharedIndexInformer are started twice and following log are output seven times.
The sharedIndexInformer has started, run more than once is not allowed
How to reproduce it (as minimally and precisely as possible):
just start vpa-admission-controller
Anything else we need to know?:
It is similar to: kubernetes-sigs/metrics-server#1002
The text was updated successfully, but these errors were encountered:
@laoj2 please take a look
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Which component are you using?:
vertical-pod-autoscaler
What version of the component are you using?:
Component version: 0.14.0
What k8s version are you using (
kubectl version
)?:kubectl version
OutputWhat environment is this in?:
AWS EKS / k3d local cluster
What did you expect to happen?:
sharedIndexInformer not started more than once
What happened instead?:
Seven sharedIndexInformer are started twice and following log are output seven times.
The sharedIndexInformer has started, run more than once is not allowed
How to reproduce it (as minimally and precisely as possible):
just start vpa-admission-controller
Anything else we need to know?:
It is similar to: kubernetes-sigs/metrics-server#1002
The text was updated successfully, but these errors were encountered: