kubernetes / community

Kubernetes community content
Apache License 2.0
11.99k stars 5.17k forks source link

VPA recommender #2732

Closed ghost closed 6 years ago

ghost commented 6 years ago

Hello all, /sig autoscaling I am using VPA autoscaling in my kubernetes cluster. Can anyone tell me why the VPA recommender is keep on allocating the memory infinitely. Actually my worker node is of 11gb memory. I am using two pods each of 4gb memory. But my VPA recommender target memory is getting allocated till 256Gb and more.

apiVersion: poc.autoscaling.k8s.io/v1alpha1 kind: VerticalPodAutoscaler metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"poc.autoscaling.k8s.io/v1alpha1","kind":"VerticalPodAutoscaler","metadata":{"annotations":{},"name":"fivehundredmb-vpa","namespace":"default"},"spec":{"selector":{"matchLabels":{"app":"fivehundred_mb"}},"updatePolicy":{"updateMode":"Auto"}}} creationTimestamp: 2018-09-27T20:37:07Z generation: 1 name: fivehundredmb-vpa namespace: default resourceVersion: "1195" selfLink: /apis/poc.autoscaling.k8s.io/v1alpha1/namespaces/default/verticalpodautoscalers/fivehundredmb-vpa uid: 1996898e-c295-11e8-a291-3c9509635c25 spec: selector: matchLabels: app: fivehundred_mb updatePolicy: updateMode: Auto status: conditions:

apiVersion: poc.autoscaling.k8s.io/v1alpha1 kind: VerticalPodAutoscaler metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"poc.autoscaling.k8s.io/v1alpha1","kind":"VerticalPodAutoscaler","metadata":{"annotations":{},"name":"fivehundredmb-vpa","namespace":"default"},"spec":{"selector":{"matchLabels":{"app":"fivehundred_mb"}},"updatePolicy":{"updateMode":"Auto"}}} creationTimestamp: 2018-09-27T20:37:07Z generation: 1 name: fivehundredmb-vpa namespace: default resourceVersion: "1361" selfLink: /apis/poc.autoscaling.k8s.io/v1alpha1/namespaces/default/verticalpodautoscalers/fivehundredmb-vpa uid: 1996898e-c295-11e8-a291-3c9509635c25 spec: selector: matchLabels: app: fivehundred_mb updatePolicy: updateMode: Auto status: conditions:

apiVersion: poc.autoscaling.k8s.io/v1alpha1 kind: VerticalPodAutoscaler metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"poc.autoscaling.k8s.io/v1alpha1","kind":"VerticalPodAutoscaler","metadata":{"annotations":{},"name":"fivehundredmb-vpa","namespace":"default"},"spec":{"selector":{"matchLabels":{"app":"fivehundred_mb"}},"updatePolicy":{"updateMode":"Auto"}}} creationTimestamp: 2018-09-27T20:37:07Z generation: 1 name: fivehundredmb-vpa namespace: default resourceVersion: "1542" selfLink: /apis/poc.autoscaling.k8s.io/v1alpha1/namespaces/default/verticalpodautoscalers/fivehundredmb-vpa uid: 1996898e-c295-11e8-a291-3c9509635c25 spec: selector: matchLabels: app: fivehundred_mb updatePolicy: updateMode: Auto status: conditions:

apiVersion: poc.autoscaling.k8s.io/v1alpha1 kind: VerticalPodAutoscaler metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"poc.autoscaling.k8s.io/v1alpha1","kind":"VerticalPodAutoscaler","metadata":{"annotations":{},"name":"fivehundredmb-vpa","namespace":"default"},"spec":{"selector":{"matchLabels":{"app":"fivehundred_mb"}},"updatePolicy":{"updateMode":"Auto"}}} creationTimestamp: 2018-09-27T20:37:07Z generation: 1 name: fivehundredmb-vpa namespace: default resourceVersion: "9907" selfLink: /apis/poc.autoscaling.k8s.io/v1alpha1/namespaces/default/verticalpodautoscalers/fivehundredmb-vpa uid: 1996898e-c295-11e8-a291-3c9509635c25 spec: selector: matchLabels: app: fivehundred_mb updatePolicy: updateMode: Auto status: conditions:

k8s-ci-robot commented 6 years ago

@nithya-krish: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either: 1. mentioning a sig: `@kubernetes/sig--` e.g., `@kubernetes/sig-contributor-experience-` to notify the contributor experience sig, OR 2. specifying the label manually: `/sig ` e.g., `/sig scalability` to apply the `sig/scalability` label Note: Method 1 will trigger an email to the group. See the [group list](https://git.k8s.io/community/sig-list.md). The `` in method 1 has to be replaced with one of these: _**bugs, feature-requests, pr-reviews, test-failures, proposals**_ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
cblecker commented 6 years ago

@nithya-krish If you believe this is a bug, this should reside as an issue against kubernetes/kubernetes, rather than this repo.

/close

k8s-ci-robot commented 6 years ago

@cblecker: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/2732#issuecomment-426013479): >@nithya-krish If you believe this is a bug, this should reside as an issue against kubernetes/kubernetes, rather than this repo. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.