Succeeded jobs contribute to node CPU request value

[KarooolisZi]

Describe the bug
Hello all. I came across a strange thing on one of our cluster nodes in Lens. Node has 2 CPU and kubectl describe node command outputs correct CPU metrics. However, in Lens GUI it says around 30 CPU on request. Node itself has plenty of succeeded jobs. However, logically it should not accumulate metrics from completed jobs. Default Lens metrics measurement is used.

To Reproduce
Steps to reproduce the behavior:

1. Create multiple jobs on one node with CPU request value set and wait till they are completed
2. Choose this node and monitor its CPU request metric
3. Use kubectl describe node command to double-check whether CPU request data matches

Expected behavior
CPU request metrics should match metrics from kubectl describe node outputs.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• Lens Version: 2024.5.271333-latest
• OS: Windows 10 Pro
• Installation method (e.g. snap or AppImage in Linux): .exe download from official website

[Tixon123]

Hello KarooolisZi,

Thank you for reaching out to Lens support!

Thank you for reporting a bug.

We are working on your issue. Stand by for further updates.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

[brgrz]

The same cumulative display from Succeeded pods happens for memory metric too.