Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display resource usage in namespace overview #2992

Open
dbadura opened this issue Jun 21, 2024 · 1 comment
Open

Display resource usage in namespace overview #2992

dbadura opened this issue Jun 21, 2024 · 1 comment
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@dbadura
Copy link
Contributor

dbadura commented Jun 21, 2024

Description

The namespace overview should have two charts with current resource status:

  • one with all limits from all pods in given namespace compared to the current resource usage taken from metrics server.
  • one with all requests from all pods in given namespace compared to the current resource usage taken from metrics server.

Remove current resource quota charts as they are not needed.

Reasons

Current resource quota charts display not very precise information about current cluster status.
It would be more usefull to see current utilization vs pod resources.

Attachments

The resource usage can be fetched by kubectl top pod.
Run kubectl -v 10 top pod to see what information is fetched from api server.

@mrCherry97 mrCherry97 added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 26, 2024
@mrCherry97 mrCherry97 changed the title feat: Display resource usage in namespace overview Display resource usage in namespace overview Jul 4, 2024
@mrCherry97 mrCherry97 self-assigned this Jul 4, 2024
@mrCherry97
Copy link
Contributor

We need to discuss, because could resolved #3016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants