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

Used ephemeral storage within kubectl top pod command #1696

Open
3deep5me opened this issue Jan 3, 2025 · 1 comment
Open

Used ephemeral storage within kubectl top pod command #1696

3deep5me opened this issue Jan 3, 2025 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@3deep5me
Copy link

3deep5me commented Jan 3, 2025

What would you like to be added:
It would be great to get also the current ephemeral storage usage with kubectl top pods command.

Why is this needed:
This would give useres/me the option to quickly get an estimate for setting requests-and-limits-for-local-ephemeral-storage .

@3deep5me 3deep5me added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 3, 2025
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 3, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants