Autoscaling components for Kubernetes

38 Open Issues Need Help Last updated: Jul 10, 2026

Open Issues Need Help

View All on GitHub
help wanted area/vertical-pod-autoscaler kind/bug area/vertical-pod-autoscaler/prometheus

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/documentation good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue triage/accepted

Autoscaling components for Kubernetes

Go
Remove redundant logs about 1 month ago
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/bug triage/needs-information

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/documentation area/vertical-pod-autoscaler/prometheus

Autoscaling components for Kubernetes

Go
help wanted kind/documentation good first issue triage/accepted

Autoscaling components for Kubernetes

Go

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/documentation good first issue

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/bug area/helm-charts

Autoscaling components for Kubernetes

Go
help wanted area/cluster-autoscaler kind/bug good first issue area/core-autoscaler triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/cluster-autoscaler kind/bug good first issue area/core-autoscaler triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/documentation good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler good first issue

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/bug needs-triage

Autoscaling components for Kubernetes

Go
help wanted area/cluster-autoscaler kind/feature area/core-autoscaler

Autoscaling components for Kubernetes

Go
VPA Helm Chart 7 months ago
help wanted area/vertical-pod-autoscaler lifecycle/rotten

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/cleanup triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/feature good first issue triage/accepted

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/feature

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler good first issue triage/accepted

Autoscaling components for Kubernetes

Go

AI Summary: The VPA updater component is generating excessive logs with the error "Failed to get parent controller for [static] pods" in version v1.4.1. This issue persists despite a previous fix (PR #7632) that was expected to handle `NodeInvalidOwnerError` for static pods with `ownerRef: Node` gracefully, indicating the fix is not working as anticipated.

Complexity: 3/5
help wanted area/vertical-pod-autoscaler kind/bug triage/accepted

Autoscaling components for Kubernetes

Go
help wanted good first issue triage/accepted area/helm-charts

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/feature lifecycle/rotten

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/bug

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/feature lifecycle/rotten

Autoscaling components for Kubernetes

Go
help wanted area/vertical-pod-autoscaler kind/bug good first issue triage/accepted

Autoscaling components for Kubernetes

Go

AI Summary: This issue proposes migrating the `vertical-pod-autoscaler` component from the unmaintained `github.com/golang/mock` library to `github.com/uber-go/mock`. The change is necessary due to the original library's lack of maintenance, as indicated by a provided screenshot. This task will involve updating dependencies and potentially refactoring existing mock implementations and generation.

Complexity: 3/5
help wanted area/vertical-pod-autoscaler kind/bug triage/accepted

Autoscaling components for Kubernetes

Go

AI Summary: This task involves deprecating the `Auto` value in the `UpdateMode` field of the Vertical Pod Autoscaler (VPA) API. This requires updating documentation to reflect the deprecation, adding warnings and log messages within the VPA controller when `Auto` is used, and creating a unit test to verify the deprecation warning functionality. The deprecation will be phased in, starting with warnings.

Complexity: 4/5
help wanted area/vertical-pod-autoscaler good first issue kind/api-change

Autoscaling components for Kubernetes

Go