Kubernetes : Deploy Metrics Server2026/05/14 |
|
Deploy Metrics Server to monitor CPU and Memory resources in Kubernetes Cluster. This example is based on the environment like follows.
+----------------------+ +----------------------+
| [ ctrl.srv.world ] | | [ dlp.srv.world ] |
| Manager Node | | Control Plane |
+-----------+----------+ +-----------+----------+
eth0|10.0.0.25 eth0|10.0.0.30
| |
------------+--------------------------+-----------
| |
eth0|10.0.0.51 eth0|10.0.0.52
+-----------+----------+ +-----------+----------+
| [ node01.srv.world ] | | [ node02.srv.world ] |
| Worker Node#1 | | Worker Node#2 |
+----------------------+ +----------------------+
|
| [1] | Deploy Metrics Server. |
|
ubuntu@ctrl:~$ git clone https://github.com/kubernetes-sigs/metrics-server
ubuntu@ctrl:~$
vi ./metrics-server/manifests/base/deployment.yaml
.....
.....
containers:
- name: metrics-server
image: gcr.io/k8s-staging-metrics-server/metrics-server:master
imagePullPolicy: IfNotPresent
args:
- --cert-dir=/tmp
- --secure-port=10250
- --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
- --kubelet-use-node-status-port
- --metric-resolution=15s
# line 29 : add
- --kubelet-insecure-tls
ubuntu@ctrl:~$ kubectl apply -k ./metrics-server/manifests/base/ # Warning: 'commonLabels' is deprecated. Please use 'labels' instead. Run 'kustomize edit fix' to update your Kustomization automatically. serviceaccount/metrics-server created clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created clusterrole.rbac.authorization.k8s.io/system:metrics-server created rolebinding.rbac.authorization.k8s.io/metrics-server-auth-reader created clusterrolebinding.rbac.authorization.k8s.io/metrics-server:system:auth-delegator created clusterrolebinding.rbac.authorization.k8s.io/system:metrics-server created service/metrics-server created deployment.apps/metrics-server created apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io createdubuntu@ctrl:~$ kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-589f44dc88-69rnb 1/1 Running 1 (38m ago) 44h
coredns-589f44dc88-lcgqc 1/1 Running 1 (38m ago) 44h
etcd-dlp.srv.world 1/1 Running 1 (38m ago) 44h
kube-apiserver-dlp.srv.world 1/1 Running 1 (38m ago) 44h
kube-controller-manager-dlp.srv.world 1/1 Running 1 (38m ago) 44h
kube-proxy-758rn 1/1 Running 1 (38m ago) 44h
kube-proxy-zblkn 1/1 Running 1 (37m ago) 44h
kube-proxy-zkvbq 1/1 Running 1 (37m ago) 44h
kube-scheduler-dlp.srv.world 1/1 Running 1 (38m ago) 44h
metrics-server-54bf87486c-7qctk 1/1 Running 0 68s
# [metrics-server] pod has been deployed
|
| [2] | To display CPU and Memory resources, run like follows. |
|
ubuntu@ctrl:~$ kubectl top node NAME CPU(cores) CPU(%) MEMORY(bytes) MEMORY(%) dlp.srv.world 66m 0% 2504Mi 16% node01.srv.world 17m 0% 1021Mi 6% node02.srv.world 12m 0% 969Mi 6%ubuntu@ctrl:~$ kubectl top pod -n kube-system NAME CPU(cores) MEMORY(bytes) coredns-589f44dc88-69rnb 1m 85Mi coredns-589f44dc88-lcgqc 1m 14Mi etcd-dlp.srv.world 12m 92Mi kube-apiserver-dlp.srv.world 25m 496Mi kube-controller-manager-dlp.srv.world 7m 131Mi kube-proxy-758rn 1m 67Mi kube-proxy-zblkn 1m 68Mi kube-proxy-zkvbq 1m 67Mi kube-scheduler-dlp.srv.world 4m 71Mi metrics-server-54bf87486c-7qctk 2m 19Mi |
| Sponsored Link |
|
|