-
Notifications
You must be signed in to change notification settings - Fork 937
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
add NODE info for kubectl top pod
output
#1706
Comments
I have worked on this feature and ready to contribute my implementation via a pull request. |
/sig cli |
@kubernetes/sig-cli-kubectl-maintainers |
Maybe we should listen to some use cases. I don't know the necessary relationship of adding node info. Although feature is not big, we should not provide feature without describing clearly. |
@kubernetes/sig-cli-kubectl-maintainers |
/triage accepted |
The implementation will be similar to kubernetes/kubernetes#126529 |
Maybe @qyecst has already invested himself in this work. Are you still involved in it? |
@googs1025 Yes, but needs to be modified to use a flag like |
/assign @qyecst |
What would you like to be added:
Hi team, I want to add NODE info for
kubectl top pod
output likeWhy is this needed:
Convenient to view the pod status of the specified node:
kubectl top pod |grep node-name
Convenient to check the load and node distribution of pods:
kubectl top pod -l app=label
When sudden surge in node load, convenient to check the status of the corresponding pods.
The current output does not include node information. When we need to handle high-load pods or pods on high-load nodes, we need to use the
kubectl get
command to obtain the node where the pod is located.This involves many additional commands and operations, such as handling and merging information from
get pod
andget podmetrics
.Using Prometheus for information aggregation is a solution, but it still takes a lot of time to pass pod names between Prometheus and the terminal when you need to operate on pods, especially when there are many pods involved.
The text was updated successfully, but these errors were encountered: