gardener-attic / vpa-exporter Goto Github PK

Describe the bug:
For the deleted VPA resources, that last recorded metrics are continued to be reported unless the vpa-exporter is restarted.

Expected behaviour:
Metrics should not be reported for VPA resources after they are deleted.

How To Reproduce (as minimally and precisely as possible):

1. Deploy vpa-exporter and a sample VPA resource.
2. Verify the metrics reported by vpa-exporter for the deployed sample VPA resource.
3. Delete the sample VPA resource.
4. Verify the metrics reported by vpa-exporter for the deleted sample VPA resource.

Logs:

Screenshots (if applicable):

Anything else we need to know?:

Feature (What you would like to be added):
Currently the vpa-exporter is logging as info

I0101 01:02:03.123456       1 main.go:241] Successfully synced 'shoot--project--shoot/*-vpa'

The problem is that in relatively small seed cluster, there are too much such logs:

$ kubectl -n garden logs vpa-exporter-57478fc75d-g4jfd --since 10m | grep 'Successfully\ synced' -c
2898

Motivation (Why is this needed?):
To reduce the volume of debug logs

Approach/Hint to the implement solution (optional):
Switch the debug level for these log messages to Debug.

Do we have a helm chart available for VPA-exporter

Need to increase the memory limits of vpa-exporter to avoid frequent OOMKill of the component

Feature (What you would like to be added):
Add message about favoring kube-state-metrics

Motivation (Why is this needed?):
I see that it is mentioned that this is being deprecated in favor of kube-state-metrics, however it's not clear currently whether this is the case by reading the documentation. My initial search for such exporter brings me to here and I couldn't find this collector in kube-state-metrics at first.

Approach/Hint to the implement solution (optional):
If it is indeed being deprecated, could we have some banner in the README suggesting others to enable the vpa collector in kube-state-metrics instead?

Feature (What you would like to be added):
Release a container image for vpa-exporter as part of release assets.

Motivation (Why is this needed?):
Usually vpa-exporter will be deployed inside a kubernetes cluster. It would be easier for the deployment if there is a container image coming with a release.

Approach/Hint to the implement solution (optional):
This can be done through github Actions along with github container registry ghcr.io.