Closed bcbrockway closed 3 years ago
VPA uses the Deployment's selector to figure out which pods to take into account when providing recommendations. My guess is that your deployments label selector selects some pods from other deployments/statefulsets as well. Selector:
selector:
matchLabels:
app.kubernetes.io/environment: dev
app.kubernetes.io/instance: elastic-logs
app.kubernetes.io/name: elastic-logs
app.kubernetes.io/part-of: eck-logs
app.mintel.com/owner: sre
You can use kubectl to verify this.
$ kubectl get pods --selector="<deployments selector>"
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
Hi all,
Got a bit of a weird bug using GKE's VPA implementation; hopefully it's still relevant here. I've created the following VPA object which has returned some recommendations as follows:
However if I look at the Deployment
targetRef
is looking for, only one of these containers exists:There are no other deployments with the same name on the whole cluster:
Our kibana (
elastic-logs-kb
) deployment and elasticsearch (elastic-logs-es-data1
/elastic-logs-es-master
) statefulsets do have those containers in their manifests so it looks like it's pulling them from there for some reason. The elasticsearch/kibana workloads are created through the elasticsearch eck operator.Stumped as to why the VPA should be picking these up... Any ideas?