-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
cpu and memory are not displayed correctly #1428
Comments
/triage accepted |
/assign @ricardoapl |
@dashpole: GitHub didn't allow me to assign the following users: ricardoapl. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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/test-infra repository. |
/assign |
Hello @a5116638, I cannot reproduce your issue with either v0.7.0 or v0.6.4. Can you please share more details (e.g. environment, configuration, versions, etc.)? |
Seems to be fine to me after deploying a 2-worker-node KinD cluster on it! ❯ kubectl top node
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
dev-2-control-plane 53m 5% 748Mi 38%
dev-2-worker 7m 0% 220Mi 11%
dev-2-worker2 11m 1% 187Mi 9% KinD cluster config # three node (two workers) cluster config
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: worker
- role: worker Kind version info ❯ kind version
kind v0.20.0 go1.20.4 darwin/arm64 K8s version info ❯ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.2", GitCommit:"846602e50eb29ecdc7441ebed2fc846048959eaa", GitTreeState:"clean", BuildDate:"2023-03-08T16:33:41Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.3", GitCommit:"25b4e43193bcda6c7328a6d147b1fb73a33f1598", GitTreeState:"clean", BuildDate:"2023-06-15T00:38:14Z", GoVersion:"go1.20.5", Compiler:"gc", Platform:"linux/arm64"}
WARNING: version difference between client (1.25) and server (1.27) exceeds the supported minor version skew of +/-1
|
I suggest we close this issue Please reopen and share more details if this is still affecting you @a5116638 /close |
@ricardoapl: You can't close an active issue/PR unless you authored it or you are a collaborator. In response to this:
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/test-infra repository. |
I encountered a problem. The cpu and memory of each node always show the same value. How should I solve it?
root@k8s-master:/etc/kubernetes# kubectl top no
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
k8s-master 217m 10% 1367Mi 73%
k8s-worker1 217m 10% 1367Mi 159%
k8s-worker2 217m 10% 1367Mi 159%
The text was updated successfully, but these errors were encountered: